dbcve.org
AvroApplication · Apache

CVE-2024-47561

HIGH · 7.3 CVSS v3.1 Published 2024-10-03
Fix available
A fix is available. Upgrade to 1.11.4 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

Apache Avro Java SDK versions 1.11.3 and earlier contain a code injection vulnerability in the schema parsing functionality. Maliciously crafted Avro schema definitions can be leveraged to execute arbitrary code on systems processing untrusted schemas.

MitigationUpgrade Apache Avro Java SDK to version 1.11.4 or 1.12.0 to resolve the vulnerability. Audit all code paths that parse untrusted Avro schemas.

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
Affected:< 1.11.4
Active Iq Unified ManagerApplication
Affected:all versions
Brocade San NavigatorApplication
Affected:all versions

CVSS 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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Avro Java SDK version
    Inspect the Avro JAR file manifest (META-INF/MANIFEST.MF) for the Implementation-Version attribute, or run 'jar -xf avro-*.jar META-INF/MANIFEST.MF' to extract and read the version. If using Maven, run 'mvn dependency:tree | grep avro' to list the avro dependency and its resolved version.
    Affected if The detected version is 1.11.3 or earlier (any version < 1.11.4)
  2. Locate all Avro JAR files in the deployment
    Search the filesystem for avro-*.jar files: 'find / -name "avro-*.jar" 2>/dev/null' on Unix systems or 'Get-ChildItem -Recurse -Filter "avro*.jar"' in PowerShell on Windows. Check application lib directories, classpaths, and bundled dependencies.
    Affected if Any avro-*.jar file found resolves to version < 1.11.4
  3. Identify code paths that parse Avro schemas
    Review application source code for calls to schema parsing APIs such as Schema.parse(), Schema.Parser.parse(), or equivalent methods that accept schema input. Search for imports of org.apache.avro.Schema and usage of ParseSchema or related methods.
    Affected if The application parses Avro schemas from any untrusted or external input sources
  4. Verify schema input source trust boundary
    Examine how Avro schemas are loaded: check if schemas originate from user input, files, network endpoints, or other untrusted sources. Look for Schema.Parser() constructors that accept File, InputStream, or String parameters directly without validation.
    Affected if Untrusted schema definitions (from users, external files, APIs) are processed without sanitization

You are affected if any Apache Avro Java SDK installation in your environment resolves to version 1.11.3 or earlier AND your system processes Avro schemas from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.11.4 or later
Fixed in 1.11.4
Interim mitigation

Upgrade Apache Avro Java SDK to version 1.11.4 or 1.12.0 to resolve the vulnerability. Audit all code paths that parse untrusted Avro schemas.

Recommended fix High confidence

Apache Avro 1.11.4 or 1.12.0

  1. 1. Identify all Java applications and systems that depend on the Apache Avro library
  2. 2. Determine the current Avro version in use (check Maven pom.xml, Gradle build.gradle, or JAR manifest files)
  3. 3. For Maven projects: update the avro dependency to version 1.11.4 or higher in pom.xml (e.g., <version>1.11.4</version>)
  4. 4. For Gradle projects: update the avro dependency to version 1.11.4 or higher in build.gradle (e.g., implementation 'org.apache.avro:avro:1.11.4')
  5. 5. Rebuild all affected Java applications
  6. 6. Redeploy the updated applications to all environments
  7. 7. Verify application functionality and run integration tests
  8. 8. For NetApp Active Iq Unified Manager and Brocade San Navigator: contact respective vendors (NetApp, Broadcom) for product-specific patches as no version-based upgrade is available for these products
Caveat Review release notes for 1.11.4 and 1.12.0 for potential API changes; 1.12.0 may include additional features beyond security fixes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47561 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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