HttpApplication · Hyper
CVE-2019-25009
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 http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.
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 http crate before version 0.1.20 has a soundness vulnerability in the HeaderMap::Drain API that uses a raw pointer, which bypasses Rust's memory safety guarantees and could lead to undefined behavior.
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
HttpApplication
< 0.1.20CVSS 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.1/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 http crate version in Cargo.lockOpen Cargo.lock file in your project root and search for the [[package]] entry with name "http". Read the version number from the version field (e.g., version = "0.1.19")Affected if The version listed is less than 0.1.20 (e.g., 0.1.19, 0.1.18, etc.)
-
Check Cargo.toml for http dependencyInspect your project's Cargo.toml file under [dependencies] or [dev-dependencies] to see if the http crate is explicitly listed and what version constraint is specifiedAffected if A version requirement like "0.1" or "<0.2" allows versions below 0.1.20
-
Identify HeaderMap::Drain usage in codeSearch your source code files for instances of "HeaderMap::Drain" or ".drain()" method calls on HeaderMap types. This API is used to iterate over and remove headers.Affected if Your codebase contains calls to HeaderMap::Drain or the drain method on HeaderMap objects
-
Verify Rust edition and unsafe codeCheck if your project or any dependency uses unsafe blocks, particularly in code that handles HTTP headers. The vulnerability involves raw pointer usage in the Drain implementation.Affected if Unsafe code interacts with HeaderMap and the http crate version is below 0.1.20
You are affected if your project uses the http crate version below 0.1.20 AND makes use of the HeaderMap::Drain API or the drain method on HeaderMap types.
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.20
Update the http crate dependency to version 0.1.20 or later to obtain the patched HeaderMap::Drain implementation.
http crate version 0.1.20
- Update the http crate dependency in Cargo.toml to version 0.1.20 or later (e.g., http = "0.1.20")
- Run `cargo update http` to update the Cargo.lock file
- Run `cargo build` or `cargo test` to verify the application compiles and tests pass with the updated dependency
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Http
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25009 — 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-25009 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