CVE-2022-35724 — apache-avro
HIGHCVE-2022-35724 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in apache-avro. A fix is available for apache-avro — see the affected versions and patch details below.
Apache Avro Rust SDK vulnerable to reader looping in cycle endlessly, consuming CPU
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
apache-avroReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
It 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | apache-avro | all versions | 0.14.0cargo update -p apache-avro --precise 0.14.0 |
Affected Products
avroapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-avro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apache-avro to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35724 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-35724 in your dependencies?
Find it across crates.io, including transitive dependencies.