Lucene search

K
githubGitHub Advisory DatabaseGHSA-3HWC-RQWP-V36Q
HistoryFeb 09, 2024 - 6:31 p.m.

Apache Solr can leak certain passwords due to System Property redaction logic inconsistencies

2024-02-0918:31:07
CWE-522
GitHub Advisory Database
github.com
13
apache solr
information leakage
vulnerability
sensitive system properties
authorization
configuration
upgrade
redaction logic

CVSS3

7.5

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

AI Score

7.1

Confidence

High

EPSS

0.001

Percentile

44.8%

Insufficiently Protected Credentials vulnerability in Apache Solr.

This issue affects Apache Solr from 6.0.0 through 8.11.2, from 9.0.0 before 9.3.0.
One of the two endpoints that publishes the Solr processā€™ Java system properties, /admin/info/properties, was only setup to hide system properties that had ā€œpasswordā€ contained in the name.
There are a number of sensitive system properties, such as ā€œbasicauthā€ and ā€œaws.secretKeyā€ do not contain ā€œpasswordā€, thus their values were published via the ā€œ/admin/info/propertiesā€ endpoint.
This endpoint populates the list of System Properties on the home screen of the Solr Admin page, making the exposed credentials visible in the UI.

This /admin/info/properties endpoint is protected under the ā€œconfig-readā€ permission.
Therefore, Solr Clouds with Authorization enabled will only be vulnerable through logged-in users that have the ā€œconfig-readā€ permission.
Users are recommended to upgrade to version 9.3.0 or 8.11.3, both of which fix the issue.
A single option now controls hiding Java system property for all endpoints, ā€œ-Dsolr.hiddenSysPropsā€.
By default all known sensitive properties are hidden (including ā€œ-Dbasicauthā€), as well as any property with a name containing ā€œsecretā€ or ā€œpasswordā€.

Users who cannot upgrade can also use the following Java system property to fix the issue:
Ā  -Dsolr.redaction.system.pattern=.*(password|secret|basicauth).*

Affected configurations

Vulners
Node
org.apache.solrsolr-coreRange9.0.0ā€“9.3.0
OR
org.apache.solrsolr-coreRange6.0.0ā€“8.11.3
VendorProductVersionCPE
org.apache.solrsolr-core*cpe:2.3:a:org.apache.solr:solr-core:*:*:*:*:*:*:*:*

CVSS3

7.5

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

AI Score

7.1

Confidence

High

EPSS

0.001

Percentile

44.8%