Skip to content

Apachesolr exposedui templated - #71

Open
robert-doyensec wants to merge 2 commits into
masterfrom
apachesolr-exposedui-templated
Open

robert-doyensec wants to merge 2 commits into
masterfrom
apachesolr-exposedui-templated

Conversation

@robert-doyensec

@robert-doyensec robert-doyensec commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

Testbed is at doyensec/security-testbeds#50

      "networkService": {
        "networkEndpoint": {
          "type": "IP_HOSTNAME_PORT",
          "ipAddress": {
            "addressFamily": "IPV4",
            "address": "192.168.65.254"
          },
          "port": {
            "portNumber": 8081
          },
          "hostname": {
            "name": "192.168.65.254"
          }
        },
        "transportProtocol": "TCP",
        "serviceName": "http",
        "serviceContext": {
          "webServiceContext": {
          }
        }
      },
      "detectionTimestamp": "2026-10-22T15:21:52.549Z",
      "detectionStatus": "VULNERABILITY_VERIFIED",
      "vulnerability": {
        "mainId": {
          "publisher": "GOOGLE",
          "value": "ApacheSolr_LFI_SSRF_ExposedUI"
        },
        "severity": "HIGH",
        "title": "Apache Solr Exposed UI Local File Read and SSRF",
        "description": "When Apache Solr service is exposed to untrusted networks and authentication is not enabled, the exposed APIs allow attackers to enable Solr\u0027s `RemoteStreaming` service and use this service to perform Server Side Request Forgery (SSRF) and/or Local File Inclusion (LFI) attacks on the system. This is usually done using the following steps:\n\n  1. Enumerating available Solr database names by sending a request to http://[solr_service]/solr/admin/cores?indexInfo\u003dfalse\u0026wt\u003djson\n  2. Enabling `RemoteStreaming` service for a given database by sending a request to http://[solr_service]/solr/[database]/config with the following json payload `{\"set-property\":{\"requestDispatcher.requestParsers.enableRemoteStreaming\":true}}`\n  3. Reading arbitrary URL through `stream.url` parameter by sending a request to http://[solr_service]/solr/[database]/debug/dump?param\u003dContentStreams\u0026stream.url\u003d[url].\n\nSee extra details for the exact scanning traffic sent by the scanner and use them to reproduce this vulnerability.\n\nNote that in 8.11.3 and later, the option is no longer configurable by API. See https://solr.apache.org/docs/8_11_3/changes/Changes.html#v8.11.3.other_changes for more information.",
        "recommendation": "Apache Solr is acknowledged by its developers to be insecure and should never be exposed on the Internet per https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity and https://solr.apache.org/guide/8_11/securing-solr.html. It is highly recommended that the Apache Solr service is bound to localhost whenever possible and you **DO NOT** use Apache Solr for handling Confidential or Need-to-Know data."
      }
    }]
  },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant