CVE-2018-11802 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in org.apache.solr:solr-parent. A fix is available for org.apache.solr:solr-parent — see the affected versions and patch details below.
Incorrect Authorization in Apache Solr
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.solr:solr-parent☕org.apache.solr:solr-parent☕org.apache.solr:solr-core☕org.apache.solr:solr-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Apache Solr, the cluster can be partitioned into multiple collections and only a subset of nodes actually host any given collection. However, if a node receives a request for a collection it does not host, it proxies the request to a relevant node and serves the request. Solr bypasses all authorization settings for such requests. This affects all Solr versions prior to 6.6.6 and 7.7 that use the default authorization mechanism of Solr (RuleBasedAuthorizationPlugin).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.solr:solr-parent | ≥ 7.0.0&&< 7.7.0 | 7.7.0org.apache.solr:solr-parent:7.7.0 |
| ☕Maven | org.apache.solr:solr-parent | all versions | 6.6.6org.apache.solr:solr-parent:6.6.6 |
| ☕Maven | org.apache.solr:solr-core | ≥ 7.0.0&&< 7.7.0 | 7.7.0org.apache.solr:solr-core:7.7.0 |
| ☕Maven | org.apache.solr:solr-core | all versions | 6.6.6org.apache.solr:solr-core:6.6.6 |
Affected Products
solrapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.solr:solr-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.solr:solr-parent to 7.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11802 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2018-11802 in your dependencies?
Find it across Maven, including transitive dependencies.