IgniteApplication · Apache
CVE-2024-52577
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 · uneditedIn Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some Ignite endpoints. The vulnerability could be exploited if an attacker manually crafts an Ignite message containing a vulnerable object whose class is present in the Ignite server classpath and sends it to Ignite server endpoints. Deserialization of such a message by the Ignite server may result in the execution of arbitrary code on the Apache Ignite server side.
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 Ignite versions before 2.17.0 bypass Class Serialization Filters on certain endpoints. An attacker can send crafted messages containing malicious class payloads present in the server classpath, which when deserialized execute arbitrary code on the server.
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
IgniteApplication
>= 2.6.0, < 2.17.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Ignite versionLocate the ignite-core JAR file or check classpath for org.apache.ignite.internal.IgniteKernal class and extract its version. Alternatively, inspect startup logs for the Ignite version string.Affected if The installed version falls within >= 2.6.0 and < 2.17.0
-
Confirm Class Serialization Filters are configuredSearch configuration files (XML, YAML, or Spring) for properties such as ignite:binaryConfiguration with setClassFilter, or programmatic calls to GridUnsafeBinarySerializer with setClassFilter. Also check for system properties like ignite.serialization.white.list or ignite.serialization.black.list.Affected if Serialization filters are configured or custom serializers are in use, but the version is vulnerable
-
Verify deserialization is enabled on server endpointsExamine network configuration for exposed TCP/TCP SSL/Rest/Jetty endpoints. Check if NodeConfiguration allows arbitrary objects to be deserialized from client connections.Affected if Ignite server nodes accept client connections and process binary objects without additional validation beyond the flawed filters
A user is affected if running Apache Ignite version 2.6.0 through 2.16.x with Class Serialization Filters configured, where server endpoints accept untrusted binary payloads that can trigger the filter bypass during deserialization.
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 · scoped2.17.0
Upgrade to Apache Ignite 2.17.0 or later and verify that serialization filters are properly enforced across all endpoints.
2.17.0 or later
- Upgrade Apache Ignite to version 2.17.0 or later
- Test the upgrade in a non-production environment to verify compatibility with your application
- Deploy the upgraded version to production after successful testing
- Review and validate your serialization filter configurations to ensure they are properly applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ignite
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52577 — 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-2024-52577 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