AvroApplication · Apache
CVE-2022-36125
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 · uneditedIt is possible to crash (panic) an application by providing a corrupted data to be read. This issue affects Rust applications using Apache Avro Rust SDK prior to 0.14.0 (previously known as avro-rs). Users should update to apache-avro version 0.14.0 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 confidenceA vulnerability in Apache Avro Rust SDK allows remote attackers to cause a denial of service (application crash/panic) by providing malformed or corrupted Avro data for reading. The issue exists in versions prior to 0.14.0.
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
< 0.14.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
- 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.
-
Check Apache Avro Rust SDK version in dependenciesInspect your Cargo.toml file for the avro-rs or apache-avro dependency and note the version numberAffected if The version is less than 0.14.0 (e.g., 0.13.x, 0.12.x, etc.)
-
Verify version in Cargo.lockRun 'cargo tree -p avro-rs' or 'cargo tree -p apache-avro' to see the exact resolved version of the Avro library in your buildAffected if The displayed version is below 0.14.0
-
Confirm usage of Avro data reading functionalitySearch your codebase for usage of AvroReader, from_avro, read::Reader, or similar read/deserialize operations from the avro libraryAffected if Your code reads Avro data and the library version is below 0.14.0
-
Check for untrusted data input sourcesAudit your application to determine if Avro data is read from external sources such as network streams, user uploads, or files that could contain malicious contentAffected if Your application reads Avro data from untrusted sources and uses a vulnerable version
You are affected if your project depends on apache-avro or avro-rs with a version lower than 0.14.0 and your application reads Avro data, particularly from untrusted 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 · scoped0.14.0
Upgrade apache-avro (formerly avro-rs) to version 0.14.0 or later to address this vulnerability.
apache-avro version 0.14.0
- Locate the Cargo.toml file in your project
- Update the avro dependency to version 0.14.0 (or apache-avro version 0.14.0 if using the renamed crate)
- Run `cargo update` or `cargo build` to fetch the fixed version
- Verify the application compiles and passes tests after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Avro
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36125 — 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-2022-36125 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