CVE-2019-15552
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 libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.
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 confidenceA use-after-free vulnerability exists in the MultiDecoder::read function of the libflate Rust crate (versions before 0.1.25). The vulnerability allows an attacker to achieve arbitrary code execution by exploiting the memory safety issue.
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.1.14, < 0.1.25CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Cargo.lock fileSearch your project directory for a file named 'Cargo.lock'. This file records the exact versions of all Rust dependencies including libflate.Affected if The Cargo.lock file exists and contains an entry for libflate with a version below 0.1.25
-
Inspect libflate version in Cargo.lockOpen Cargo.lock and search for the 'name = "libflate"' section. Read the version number listed immediately after (e.g., version = "0.1.20").Affected if The version shown is 0.1.14 or higher but below 0.1.25 (for example, 0.1.20, 0.1.24, or any version in the range 0.1.14 to 0.1.24)
-
Check Cargo.toml for direct libflate dependencyOpen your project's Cargo.toml file and look for 'libflate' under the [dependencies] section. Note the specified version range if present.Affected if A direct dependency on libflate is declared with a version constraint like '0.1' or '>=0.1.14,<0.1.25' that would resolve to a vulnerable version
-
Identify if libflate is a transitive dependencyRun 'cargo tree -p libflate' in your project directory to see if libflate is pulled in as an indirect dependency by another crate. Check the resolved version in the output.Affected if The output shows libflate at a version in the vulnerable range (0.1.14 to 0.1.24)
You are affected if any Cargo.lock file in your project lists libflate at version 0.1.14 or higher but below 0.1.25, regardless of whether it is a direct or transitive dependency.
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.
dbcve · scoped0.1.25
Update libflate to version 0.1.25 or later. Audit all dependent crates and applications to identify those pulling in the vulnerable version, then update their direct or transitive dependencies.
libflate 0.1.25 or later
- 1. Run `cargo update` or manually update the libflate dependency in your Cargo.toml file
- 2. Change the libflate version from the current vulnerable version to 0.1.25 or later (e.g., `libflate = "0.1.25"`)
- 3. Run `cargo build` or `cargo update` to fetch the fixed version
- 4. Rebuild and test your application to verify the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15552 — 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-15552 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