CVE-2019-15549
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 · uneditedAn issue was discovered in the asn1_der crate before 0.6.2 for Rust. Attackers can trigger memory exhaustion by supplying a large value in a length field.
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 confidenceThe asn1_der Rust crate before 0.6.2 lacks proper bounds checking on ASN.1 DER length fields during parsing. Attackers can supply an excessively large value in the length field, causing the parser to attempt memory allocation beyond reasonable limits, resulting in memory exhaustion and denial of service.
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< 0.6.2CVSS 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.0/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 asn1_der dependency in Cargo.tomlSearch your project source files for 'asn1_der' in Cargo.toml dependency declarations: grep -r 'asn1_der' path/to/Cargo.tomlAffected if asn1_der is listed as a dependency with a version specifier less than 0.6.2 (for example, "0.6", "0.6.0", "0.6.1", or any <0.6.2 semver range)
-
Check resolved version in Cargo.lockFind the Cargo.lock file and locate the [[package]] entry for name = "asn1_der", then read the version fieldAffected if The version field shows a version lower than 0.6.2 (such as 0.6.1, 0.6.0, or 0.5.x)
-
Identify if crate is used for ASN.1 DER parsingSearch your codebase for imports of asn1_der functions (e.g., 'use asn1_der::') and review code that calls parsing functions on untrusted inputAffected if Your code calls asn1_der parsing functions on data from untrusted network sources or unverified files
-
Check for transitive dependency usageIf asn1_der is not a direct dependency, run 'cargo tree -p asn1_der' or examine your full dependency tree to see if any crate pulls it inAffected if asn1_der appears anywhere in the dependency tree with version < 0.6.2
You are affected if your project directly or transitively depends on the asn1_der Rust crate at a version lower than 0.6.2 and uses it to parse untrusted ASN.1 DER data.
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.
From vendor data0.6.2
Upgrade the asn1_der crate to version 0.6.2 or later, which implements proper validation and bounds checking on length fields to prevent unbounded memory allocation.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15549 — 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-2019-15549 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