dbcve.org
SolrApplication · Apache

CVE-2024-52012

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 9.8.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Relative Path Traversal vulnerability in Apache Solr. Solr instances running on Windows are vulnerable to arbitrary filepath write-access, due to a lack of input-sanitation in the "configset upload" API.  Commonly known as a "zipslip", maliciously constructed ZIP files can use relative filepaths to write data to unanticipated parts of the filesystem.   This issue affects Apache Solr: from 6.6 through 9.7.0. Users are recommended to upgrade to version 9.8.0, which fixes the issue.  Users unable to upgrade may also safely prevent the issue by using Solr's "Rule-Based Authentication Plugin" to restrict access to the configset upload API, so that it can only be accessed by a trusted set of administrators/users.

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 confidence

Relative path traversal (zipslip) vulnerability in Apache Solr's configset upload API on Windows allows attackers to write arbitrary files to the filesystem by crafting ZIP archives with relative path entries (e.g., ../../../etc/passwd). The API lacks input sanitization to validate extracted file paths.

MitigationUpgrade to Apache Solr 9.8.0 which includes the fix, or alternatively implement the Rule-Based Authentication Plugin to restrict configset upload API access to trusted administrators only.

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
Affected:>= 6.6.0, < 9.8.0

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

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

  1. Check Apache Solr version
    Run 'bin/solr version' or inspect the solr-[version].jar file in the Solr installation directory, or query the Solr API at /solr/admin/info/system
    Affected if The installed version is >= 6.6.0 and < 9.8.0
  2. Verify operating system
    Run 'uname -a' on Linux or check System Properties on Windows to confirm the OS
    Affected if The Solr instance is running on Windows (this vulnerability only affects Windows installations)
  3. Confirm configset upload API accessibility
    Check if the /solr/admin/configs endpoint is exposed without authentication or accessible to untrusted users by reviewing security.json or solr.in.sh configuration, or attempt a locally authorized curl request to POST to /solr/admin/configs/upload
    Affected if The configset upload API is accessible without proper authentication or to untrusted users

You are affected if running Apache Solr 6.6.0 to 9.7.x on Windows with the configset upload API accessible to untrusted or unauthenticated users.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.8.0 or later
Fixed in 9.8.0
Interim mitigation

Upgrade to Apache Solr 9.8.0 which includes the fix, or alternatively implement the Rule-Based Authentication Plugin to restrict configset upload API access to trusted administrators only.

Recommended fix High confidence

9.8.0

  1. 1. Back up your existing Solr data, configuration, and ZooKeeper state (if using SolrCloud mode)
  2. 2. Download Apache Solr 9.8.0 from the official Apache repository (https://solr.apache.org/downloads.html)
  3. 3. Stop the currently running Solr service or process
  4. 4. If using SolrCloud, back up the ZooKeeper configset znodes using zkCli.sh or equivalent
  5. 5. Install Solr 9.8.0 following the standard installation process for your deployment mode (standalone or SolrCloud)
  6. 6. Restore your configuration and data from the backup
  7. 7. Start the Solr service
  8. 8. Verify that the configset upload API functions correctly with legitimate configurations
Caveat Major version upgrades (e.g., 6.x/7.x to 9.x) may introduce breaking changes in API compatibility, configuration syntax, or indexing behavior; test thoroughly in a staging environment first

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52012 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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