dbcve.org
Lucene ReplicatorApplication · Apache

CVE-2024-45772

HIGH · 8.0 CVSS v3.1 Published 2024-09-30
Fix available
A fix is available. Upgrade to 9.12.0 or later.
See remediation →
82/100
Remediation priority · High
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
Deserialization of Untrusted Data vulnerability in Apache Lucene Replicator. This issue affects Apache Lucene's replicator module: from 4.4.0 before 9.12.0. The deprecated org.apache.lucene.replicator.http package is affected. The org.apache.lucene.replicator.nrt package is not affected. Users are recommended to upgrade to version 9.12.0, which fixes the issue. The deserialization can only be triggered if users actively deploy an network-accessible implementation and a corresponding client using a HTTP library that uses the API (e.g., a custom servlet and HTTPClient). Java serialization filters (such as -Djdk.serialFilter='!*' on the commandline) can mitigate the issue on vulnerable versions without impacting functionality.

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

A deserialization of untrusted data vulnerability exists in Apache Lucene Replicator's deprecated org.apache.lucene.replicator.http package (versions 4.4.0 through 9.11.x). The vulnerability can be exploited when users have deployed a network-accessible implementation using custom servlets and HTTPClient that leverage this deprecated API.

MitigationUpgrade to Lucene 9.12.0 or apply Java serialization filters (-Djdk.serialFilter='!*') as a workaround. Only deployments actively using the deprecated http package with custom network-accessible implementations are affected.

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
Lucene ReplicatorApplication
Affected:>= 4.4.0, < 9.12.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Lucene Replicator version
    Locate the lucene-replicator JAR file or dependency in your project (e.g., lucene-replicator-*.jar) and check its version number against the affected range (4.4.0 through 9.11.x)
    Affected if Installed version is 4.4.0 through 9.11.x
  2. Verify the deprecated http package is in use
    Search your codebase for imports or references to org.apache.lucene.replicator.http, or inspect the lucene-replicator JAR for the presence of the org/apache/lucene/replicator/http/ directory
    Affected if Codebase or deployed JAR contains classes from org.apache.lucene.replicator.http package
  3. Confirm custom servlet implementation exists
    Search for classes extending javax.servlet.http.HttpServlet or jakarta.servlet.http.HttpServlet that interact with the Lucene replicator http classes, or check deployed WAR files for custom servlets using the replicator API
    Affected if Custom servlet classes that utilize the deprecated http package are deployed
  4. Check for network accessibility
    Inspect your server configuration (e.g., web.xml, deployment descriptors, or network bind addresses) to determine if the servlet is exposed on a network-accessible interface rather than localhost-only
    Affected if The servlet is bound to a non-localhost network interface or exposed externally
  5. Verify HTTPClient usage with deprecated API
    Search for usage of HTTPClient (org.apache.http.impl.client.HttpClient or similar) in code that interacts with the deprecated http package, or inspect network traffic patterns if logging is enabled
    Affected if HTTPClient is used to communicate with the deprecated http endpoint

A user is affected only if they are running Lucene Replicator version 4.4.0-9.11.x AND have deployed a network-accessible implementation using custom servlets that leverage the deprecated org.apache.lucene.replicator.http API with HTTPClient.

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.12.0 or later
Fixed in 9.12.0
Interim mitigation

Upgrade to Lucene 9.12.0 or apply Java serialization filters (-Djdk.serialFilter='!*') as a workaround. Only deployments actively using the deprecated http package with custom network-accessible implementations are affected.

Recommended fix High confidence

Lucene 9.12.0

  1. Upgrade Apache Lucene Replicator to version 9.12.0 or later
  2. Verify that no custom network-accessible implementations using the deprecated org.apache.lucene.replicator.http package are in use
  3. If upgrade is not immediately possible, apply Java serialization filter by adding -Djdk.serialFilter='!*' to the JVM command line as a temporary mitigation

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

Fix this in Lucene Replicator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45772 — 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-45772 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