SolrApplication · Apache
CVE-2023-50292
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.
NVD · uneditedIncorrect Permission Assignment for Critical Resource, Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr. This issue affects Apache Solr: from 8.10.0 through 8.11.2, from 9.0.0 before 9.3.0. The Schema Designer was introduced to allow users to more easily configure and test new Schemas and configSets. However, when the feature was created, the "trust" (authentication) of these configSets was not considered. External library loading is only available to configSets that are "trusted" (created by authenticated users), thus non-authenticated users are unable to perform Remote Code Execution. Since the Schema Designer loaded configSets without taking their "trust" into account, configSets that were created by unauthenticated users were allowed to load external libraries when used in the Schema Designer. Users are recommended to upgrade to version 9.3.0, which fixes the issue.
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.
dbcve analysis · high confidenceApache Solr's Schema Designer feature bypassed trust validation when loading configSets, allowing unauthenticated users' configSets to load external libraries (normally restricted to 'trusted' configSets created by authenticated users). This authorization flaw enables Remote Code Execution for unauthenticated attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data
SolrApplication
>= 6.0.0, < 8.11.3>= 9.0.0, < 9.4.1CVSS 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.
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? 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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Apache Solr versionRun 'bin/solr version' from the Solr installation directory, or locate the solr-core-*.jar file and check its filename for the version number.Affected if The installed version falls within 6.0.0 to 8.11.2 (inclusive) or 9.0.0 to 9.4.0 (inclusive).
-
Check if unauthenticated configSet creation is allowedReview the Solr security configuration, typically in 'security.json' or via the '/solr/admin/configs' API, to determine if 'undefined' or unauthenticated users can create configSets.Affected if ConfigSets can be created or uploaded by unauthenticated or 'trusted=false' users.
-
Inspect existing configSets for trust statusList all configSets using the '/solr/admin/configs?action=LIST' API and check each configSet's 'trusted' property.Affected if There are configSets with 'trusted=false' that were created by unauthenticated users.
If running an affected Solr version AND the Schema Designer feature is accessible to unauthenticated users who can load untrusted configSets with external libraries, the environment is vulnerable to unauthenticated RCE.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped8.11.39.4.1
Upgrade Apache Solr to version 9.3.0 or later to fix the Schema Designer trust validation bypass. If immediate upgrade is not possible, disable the Schema Designer feature or ensure all configSets are created by authenticated users only.
9.3.0 (or 8.11.3 for Solr 8.x branch)
- 1. Backup your existing Solr data, configuration, and any custom configSets before proceeding with the upgrade.
- 2. Download Apache Solr version 9.3.0 (or the appropriate fixed version for your major branch: 8.11.3 for Solr 8.x) from the official Apache Solr downloads page.
- 3. Stop the running Solr instance.
- 4. Replace the existing Solr installation directory with the new version, preserving your data directory and custom configurations.
- 5. Review and update any custom configurations or configSets that may not be compatible with the new version.
- 6. Start the Solr service and verify that it starts successfully.
- 7. Test the Schema Designer functionality to confirm the fix is working (untrusted configSets should no longer be able to load external libraries).
- 8. Verify that all your collections and data are accessible and functioning correctly.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Solr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50292 in production — separate from our analysis above.
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.
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.
- 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