CVE-2024-47561 — avro
CVE-2024-47561 is a Deserialization of Untrusted Data vulnerability in org.apache.avro:avro. A fix is available for org.apache.avro:avro — see the affected versions and patch details below.
Apache Avro Java SDK: Arbitrary Code Execution when reading Avro schema (Java SDK)
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47561.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.apache.avro:avroReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Schema parsing in the Java SDK of Apache Avro 1.11.3 and previous versions allows bad actors to execute arbitrary code. Users are recommended to upgrade to version 1.11.4 or 1.12.0, which fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.avro:avro | all versions | 1.11.4org.apache.avro:avro:1.11.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.avro:avro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.avro:avro to 1.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47561 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-47561 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-47561. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The Red Hat build of Apache Camel K 1.10 was rated Important as it allows users to provide an Avro schema for parsing. Note that this functionality is limited to authenticated users. Red Hat Single Sign-On 7 ships the affected component in its maven repository but does not use it in the product. As such it is affected…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.4.3 for Spring Boot | avro | RHSA-2024:8064 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | avro | RHSA-2024:7972 |
| Red Hat build of Apicurio Registry 2.6.5 GA | see advisory | RHSA-2024:7861 |
| Red Hat build of Quarkus 3.2 | avro | RHSA-2024:7676 |
| Red Hat build of Quarkus 3.8 | avro | RHSA-2024:7670 |
| Red Hat JBoss Enterprise Application Platform | org.apache.avro/avro:1.11.4.redhat-00001 | RHSA-2024:10933 |
| Red Hat JBoss Enterprise Application Platform 7 | see advisory | RHSA-2024:7812 |
| Red Hat JBoss Enterprise Application Platform 7 | see advisory | RHSA-2024:8093 |
Frequently Asked Questions
Is CVE-2024-47561 in your dependencies?
O3 Security finds CVE-2024-47561 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.