dbcve.org
CWE-130Weakness · CWE-130

CVE-2024-53856

HIGH · 7.5 CVSS v3.1 Published 2024-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
rPGP is a pure Rust implementation of OpenPGP. Prior to 0.14.1, rPGP allows an attacker to trigger rpgp crashes by providing crafted data. This vulnerability is fixed in 0.14.1.

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

rPGP versions prior to 0.14.1 contain a vulnerability that allows remote attackers to cause denial-of-service by providing crafted OpenPGP data that triggers crashes in the library. This is a parsing/input validation issue in the pure Rust OpenPGP implementation.

MitigationUpgrade rPGP to version 0.14.1 or later. Review any systems processing untrusted OpenPGP data to ensure they handle library failures gracefully.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

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

  1. Identify rPGP usage in your environment
    Search for rPGP in your dependency files (Cargo.toml, package-lock.json, Gemfile.lock, etc.) or installed packages. Check if any application or service uses the rPGP Rust library.
    Affected if rPGP is found as a dependency
  2. Check the installed rPGP version
    Run a command to display the rPGP version from your dependency lock file or installed package. Compare against the affected range: versions prior to 0.14.1.
    Affected if The version shown is lower than 0.14.1
  3. Determine if untrusted OpenPGP data is processed
    Inspect your application code or configuration to identify if rPGP is used to parse, validate, or process OpenPGP data from external or untrusted sources.
    Affected if Your system uses rPGP to parse OpenPGP data that originates from users, networks, or other untrusted sources

You are affected if rPGP version 0.14.1 or later is not in use and your system processes untrusted OpenPGP data with the rPGP library.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade rPGP to version 0.14.1 or later. Review any systems processing untrusted OpenPGP data to ensure they handle library failures gracefully.

Recommended fix High confidence

rPGP version 0.14.1

  1. Locate the rPGP dependency in your project's Cargo.toml file
  2. Change the rPGP version specification to 0.14.1 (e.g., `rpgp = "0.14.1"`)
  3. Run `cargo update rpgp` to fetch the updated dependency
  4. Run `cargo build` to compile with the fixed version
  5. Run your application's test suite to verify functionality is not broken

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53856 — 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-53856 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