AvroApplication · Apache
CVE-2022-35724
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 provide data to be read that leads the reader to loop in cycles endlessly, consuming CPU. 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 denial-of-service vulnerability in Apache Avro Rust SDK allows malicious Avro data to trigger an infinite loop in the reader, causing CPU exhaustion. The issue stems from insufficient input validation when processing crafted data that causes cyclic looping.
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.
-
Locate Apache Avro Rust SDK usageSearch your project dependencies (Cargo.toml, Cargo.lock) or runtime environment for the 'apache-avro' crate. Also check for any Avro serialization/deserialization libraries that may depend on it.Affected if The apache-avro crate or any library depending on it is found in your project dependencies.
-
Determine installed apache-avro versionCheck your Cargo.lock file for the 'apache-avro' crate version, or run 'cargo tree -p apache-avro' to see the resolved version.Affected if The installed version is lower than 0.14.0 (e.g., 0.13.x, 0.12.x, etc.).
-
Identify if Avro reader processes external dataReview your codebase to determine if the Avro reader reads data from untrusted sources such as user uploads, external API responses, network streams, or files that could be crafted by an attacker.Affected if Your application uses the Avro reader to process data that originates from outside your trusted environment.
-
Check for reader loop conditionsInspect code paths that invoke the Avro reader (typically using read APIs like 'Reader::new' or 'from_reader'). Look for any input validation or schema enforcement before reading.Affected if The reader processes Avro data without prior validation of schema structure or data integrity, and the version is below 0.14.0.
You are affected if your environment uses apache-avro version lower than 0.14.0 and processes untrusted Avro data through the reader, as crafted data can trigger an infinite loop causing CPU exhaustion.
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 apache-avro to version 0.14.0 or later to receive the fix for this vulnerability.
apache-avro version 0.14.0
- Update the apache-avro dependency in your Cargo.toml file to version 0.14.0 or later (e.g., apache-avro = "0.14.0" or "^0.14.0")
- Run `cargo update` or `cargo build` to fetch and compile the updated dependency
- Test your application to verify the upgrade resolves the infinite loop issue and does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Avro
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35724 — 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-35724 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