LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25009: An issue was discovered in the http crate before 0.1.20 for Rust.

An issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE affects the Rust http crate before 0.1.20. The reported problem is an unsound HeaderMap::Drain API involving raw pointer use. Sources do not provide CVSS severity, confirmed exploitation, or a downstream product list, so business urgency depends on whether deployed Rust services include vulnerable versions.

Executive priority

Treat this as a dependency hygiene and exposure validation item, not an emergency from the supplied evidence. Prioritize Rust internet-facing services first.

Technical view

CVE-2019-25009 describes a soundness issue in HeaderMap::Drain in the Rust http crate before 0.1.20. The CVE source says raw pointer use can defeat Rust soundness. No CWE, CVSS vector, exploit details, or vulnerable CPEs are provided in the supplied sources.

Likely exposure

Exposure is most likely in Rust applications or services that depend directly or transitively on the http crate below 0.1.20.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation. The public details describe a library API soundness flaw, not a confirmed remote attack path.

Researcher notes

Evidence is limited to the CVE and RustSec reference. Assess reachability by identifying code paths that use HeaderMap::Drain and by reviewing transitive dependency ownership.

Mitigation direction

  • Inventory Rust projects for direct or transitive http crate usage.
  • Move dependencies off http crate versions before 0.1.20.
  • Check RustSec and project maintainers for current remediation guidance.
  • Rebuild and redeploy affected services after dependency updates.

Validation and detection

  • Review Cargo.lock and manifests for http crate versions below 0.1.20.
  • Confirm dependency resolution no longer selects affected versions.
  • Run the project’s unit and regression tests after updating dependencies.
  • Check deployed artifact SBOMs or dependency reports for remaining exposure.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-25009 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.