AvroApplication · Apache
CVE-2022-36124
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 for a Reader to consume memory beyond the allowed constraints and thus lead to out of memory on the system. 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 confidenceThe Apache Avro Rust SDK prior to version 0.14.0 fails to enforce memory allocation constraints when reading Avro data, allowing a Reader to consume excessive memory beyond allowed limits and potentially cause 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
< 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.
-
Identify apache-avro dependency in projectInspect Cargo.toml or Cargo.lock for the apache-avro crate dependency and note its version numberAffected if The apache-avro version listed is below 0.14.0
-
Locate Reader usage in codebaseSearch source files for imports or usage of avro::Reader, avro::read::Reader, or similar Reader patterns from the avro crateAffected if Codebase contains Reader implementations that read Avro data
-
Verify memory limit configurationCheck if custom memory limits or constraints are passed to the Reader API (such as max_alloc_bytes or similar limit parameters)Affected if No explicit memory constraints are configured for Reader operations and avro version is below 0.14.0
-
Confirm runtime dependency versionAt runtime or build time, query the actual loaded apache-avro library version using cargo tree, cargo list, or inspecting the built artifact metadataAffected if The resolved dependency version is below 0.14.0
A system is affected if it uses the Apache Avro Rust SDK with a version lower than 0.14.0 and utilizes Reader functionality to parse Avro data without custom memory constraints in place.
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
Update the apache-avro dependency to version 0.14.0 or later to obtain the memory constraint fix.
apache-avro version 0.14.0
- Update your Cargo.toml dependency for apache-avro to version 0.14.0 or later
- Run cargo update to fetch the new version
- Rebuild your project with cargo build to verify the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Avro
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36124 — 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-36124 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