Incorrect Authorization in Apache Solr
Apache Solr
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.solr:solr-parent Maven |
|
|
| org.apache.solr:solr-solrj Maven |
|
|
| org.apache.solr:solr-core |
Apache Solr
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.solr:solr-parent Maven |
|
|
| org.apache.solr:solr-solrj Maven |
|
|
| org.apache.solr:solr-core |
Affected Apache Solr versions restrict dangerous features in ConfigSets uploaded through the API without authentication or authorization. An unauthenticated remote attacker can circumvent those checks by combining UPLOAD and CREATE actions, potentially enabling features that could be used for remote code execution.
Teams running Apache Solr 6.6.0–6.6.6, 7.0.0–7.7.3, or 8.0.0–8.6.2, or the affected Maven packages from 6.6.0 up to but not including 8.6.3, should check their deployments.
|
|
Apache Solr versions 6.6.0 to 6.6.6, 7.0.0 to 7.7.3 and 8.0.0 to 8.6.2 prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via API without authentication/authorization. The checks in place to prevent such features can be circumvented by using a combination of UPLOAD/CREATE actions.
From the CVE record · apache