SolrApplication · Apache

CVE-2023-50291

HIGH · 7.5 CVSS v3.1 Published 2024-02-09

Fix available

A fix is available. Upgrade to 8.11.3 / 9.3.0 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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, which fixes 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).*'

Technical summary

dbcve analysis · high confidence

Apache Solr versions 6.0.0-8.11.2 and 9.0.0-9.2.x have an insufficiently protected credentials vulnerability where the /admin/info/properties endpoint only filtered system properties containing 'password' in the name. Sensitive properties like 'basicauth' and 'aws.secretKey' were exposed through this endpoint, which is protected under the 'config-read' permission, meaning only authenticated users with that permission could exploit it.

MitigationUpgrade to Solr 9.3.0 or 8.11.3, or alternatively add the JVM argument '-Dsolr.redaction.system.pattern=.*(password|secret|basicauth).*' to hide sensitive system properties.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

SolrApplication

Affected:>= 6.0.0, < 8.11.3>= 9.0.0, < 9.3.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed Apache Solr version

Run 'bin/solr version' or check the Solr admin UI version display, or inspect the 'solr-core' JAR manifest

Affected if Version is 6.0.0 through 8.11.2, or 9.0.0 through 9.2.x
Verify if authentication and authorization are enabled

Check solr.in.sh or solr.in.cmd for SOLR_AUTH_TYPE and SOLR_AUTHENTICATION_ENABLED settings, or check security.json for authorization configuration

Affected if Authentication is disabled or the config-read permission is granted to untrusted users
Inspect the /admin/info/properties endpoint response

Make an authenticated request to http://localhost:8983/solr/admin/info/properties and examine the returned system properties for any containing 'basicauth', 'aws.secretKey', or other sensitive keys that are not filtered

Affected if The response contains sensitive properties like basicauth credentials or aws.secretKey values
Check for sensitive system properties in Solr configuration

Review Solr startup scripts (solr.in.sh, solr.in.cmd) or JVM arguments for system properties that contain 'basicauth', 'secret', or 'aws' in their names

Affected if Sensitive system properties are set and the Solr version is in the affected range

A user is affected if they run a vulnerable Solr version (6.0.0-8.11.2 or 9.0.0-9.2.x) with authentication enabled that exposes the /admin/info/properties endpoint to users with config-read permission, allowing retrieval of sensitive properties like basicauth or aws.secretKey.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 8.11.3 / 9.3.0 or later

Fixed in 8.11.39.3.0

Interim mitigation

Upgrade to Solr 9.3.0 or 8.11.3, or alternatively add the JVM argument '-Dsolr.redaction.system.pattern=.*(password|secret|basicauth).*' to hide sensitive system properties.

Recommended fix High confidence

Solr 8.11.3 or Solr 9.3.0 (depending on current major version)

Upgrade to Solr 8.11.3 if running version 6.x or 7.x or 8.x (8.0.0 through 8.11.2)
Upgrade to Solr 9.3.0 if running version 9.x (9.0.0 through 9.2.x)
After upgrade, verify the /admin/info/properties endpoint no longer exposes sensitive properties like basicauth, aws.secretKey, or properties containing 'secret'
Alternatively, if upgrade is not feasible, add the JVM argument '-Dsolr.redaction.system.pattern=.*(password|secret|basicauth).*' to the Solr startup script
Restart Solr after applying the configuration workaround

Caveat Standard upgrade testing recommended; no major API changes expected from this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solr Scoped from the published advisory

Consultation3.0 h
Implementation2.0 h
Testing4.0 h
Review / QA2.0 h

11.0 hours of engineering $1,920

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2023-50291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

solr.apache.orgVendor Advisory
www.openwall.comMailing List
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50291 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-50291?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 8.11.3 / 9.3.0 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 3.3%

Affects: Solr

Remediation

A high-priority fix

Fix this in Solr 11 hrs · Moderate

Typical engagement from $1,920

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-50291 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References