AvroApplication · Apache
CVE-2023-39410
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 · uneditedWhen deserializing untrusted or corrupted data, it is possible for a reader to consume memory beyond the allowed constraints and thus lead to out of memory on the system. This issue affects Java applications using Apache Avro Java SDK up to and including 1.11.2. Users should update to apache-avro version 1.11.3 which addresses this 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 confidenceThis is a resource exhaustion vulnerability in Apache Avro Java SDK's deserialization logic. When processing untrusted or corrupted Avro data, the reader can allocate memory beyond configured limits, potentially causing out-of-memory conditions on the system.
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
AvroApplication
< 1.11.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Avro library versionInspect your project's dependency manifest: for Maven check pom.xml for 'apache-avro' or 'org.apache.avro' dependency version; for Gradle check build.gradle for 'avro' dependency; for deployed applications check the avro-*.jar file name in the classpath or lib directoryAffected if The reported version is earlier than 1.11.3 (for example 1.11.0, 1.10.2, 1.9.x, etc.)
-
Confirm Avro deserialization is in useSearch your codebase for calls to Avro deserialization methods such as DatumReader, SpecificDatumReader, GenericDatumReader, or usage of Avro deserializers in data processing pipelinesAffected if Your application performs Avro deserialization to read Avro data into Java objects
-
Verify data source trustworthinessReview whether your Avro deserialization reads data from external untrusted sources, network streams, user-uploaded files, or any data source outside your trusted environmentAffected if Your application deserializes Avro data from untrusted or external sources
You are affected if your Apache Avro library version is earlier than 1.11.3 and your application performs Avro deserialization on untrusted or external data sources.
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 · scoped1.11.3
Update apache-avro library to version 1.11.3 or later to patch the unbounded memory allocation during deserialization.
apache-avro 1.11.3
- Update the Apache Avro dependency in your Maven pom.xml (or equivalent build file) to version 1.11.3
- Run a Maven/Gradle dependency update to fetch the new avro-1.11.3 library
- Rebuild and recompile your Java application to ensure the new library is included
- Restart any Java services or applications that use the Avro library
- Verify the application starts and functions correctly with the updated library
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Avro
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39410 — 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-39410 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