Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-13647

CVE-2019-12409: Apache Solr RCE vulnerability due to bad config default

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 8.1.1
    • Fix Version/s: 8.3
    • Component/s: None
    • Labels:
      None

      Description

      This issue originally had the title "default solr.in.sh contains uncommented lines" and told users to check their solr.in.sh file. Later we upgraded the severity of this due to risk of remote code execution, acquired a CVE number and issued the public annoucement quoted below.

      CVE-2019-12409: Apache Solr RCE vulnerability due to bad config default
      
      Severity: High
      
      Vendor:
      The Apache Software Foundation
      
      Versions Affected:
      Solr 8.1.1 and 8.2.0 for Linux
      
      Description: The 8.1.1 and 8.2.0 releases of Apache Solr contain an
      insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option
      in the default solr.in.sh configuration file shipping with Solr.
      
      Windows users are not affected.
      
      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 vulnerability is already public [1] and mitigation steps were
      announced on project mailing lists and news page [3] on August 14th,
      without mentioning RCE at that time.
      
      Mitigation:
      Make sure your effective solr.in.sh file has ENABLE_REMOTE_JMX_OPTS set
      to 'false' on every Solr node and then restart Solr. Note that the
      effective solr.in.sh file may reside in /etc/defaults/ or another
      location depending on the install. You can then 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.
      
      There is no need to upgrade or update any code.
      
      Remember to follow the Solr Documentation's advice to never expose Solr
      nodes directly in a hostile network environment.
      
      Credit:
      Matei "Mal" Badanoiu
      Solr JIRA user 'jnyryan' (John)
      
      References:
      [1] https://issues.apache.org/jira/browse/SOLR-13647
      [3] https://lucene.apache.org/solr/news.html
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                janhoy Jan H√łydahl
                Reporter:
                jnyryan John
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 10m
                  1h 10m