Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


09:00 AM
Larry Loeb
Larry Loeb
Larry Loeb

Solr Search Tool Can Allow Remote Code Execution (RCE) by Default

A security vulnerability affecting the Linux enterprise search tool Apache Solr has been reclassified by Tenable as 'high severity status.'

A security vulnerability affecting the Linux enterprise search tool Apache Solr has been reclassified by Tenableas "high severity status." It seems that the default configuration of Solr on Solr 8.1.1 and 8.2.0 for Linux (but not for Windows) allows a remote code execution (RCE).

The NoSQL tool has been maintained since 2006 by open-source organization Apache Software Foundation, news organization CNET having donated it after building on Apache's Lucene. The ASF team has issued an advisory about the situation.

The team describes the vuln as, "If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server."

The vuln has become recognized as more serious than initially thought when reports of it emerged this past July. It was then thought that it would only allow cybercriminals or other third parties to access monitoring data. However, a full-blown hole was found to exist on port 8983 that would allow RCE to happen.

A revised proof-of-concept has been put up on GitHub showing how such an attack could proceed.

Mitigation for this situation is fairly simple, but may be a bit complicated to implement. The team advises that users should make sure that the effective solr.in.sh file has ENABLE_REMOTE_JMX_OPTS set to "false" on every Solr node and then restart Solr. The effective solr.in.sh file may reside in /etc/defaults/ or another location depending on the install. As a check, validate that the "com.sun.management.jmxremote" family of properties are not listed in the "Java Properties" section of the Solr Admin UI, or configured in a secure way.

Though the team recommends upgrading to version 8.3 because of all the feature modifications they have done, Tenable thinks that 8.3 will still allow the vuln to be active if it is default configured.

Tenable points out that adding authentication to an instance may help. They also note that "unless the Config API is locked down, an attacker could modify the solrconfig.xml file."

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Threaded  |  Newest First  |  Oldest First
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-10-19
Truncated L2CAP K-frame causes assertion failure. Zephyr versions >= 2.4.0, >= v.2.50 contain Improper Handling of Length Parameter Inconsistency (CWE-130), Reachable Assertion (CWE-617). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-fx88-6c29-...
PUBLISHED: 2021-10-19
Disconnecting L2CAP channel right after invalid ATT request leads freeze. Zephyr versions >= 2.4.0, >= 2.5.0 contain Use After Free (CWE-416). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7g38-3x9v-v7vp
PUBLISHED: 2021-10-19
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is c...
PUBLISHED: 2021-10-19
In broadband environments, including but not limited to Enhanced Subscriber Management, (CHAP, PPP, DHCP, etc.), on Juniper Networks Junos OS devices where RADIUS servers are configured for managing subscriber access and a subscriber is logged in and then requests to logout, the subscriber may be fo...
PUBLISHED: 2021-10-19
An Incorrect Behavior Order vulnerability in the MAP-E automatic tunneling mechanism of Juniper Networks Junos OS allows an attacker to send certain malformed IPv4 or IPv6 packets to cause a Denial of Service (DoS) to the PFE on the device which is disabled as a result of the processing of these pac...