CVE-2019-16140
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 chttp crate before 0.1.3 for Rust. There is a use-after-free during buffer conversion.
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 confidenceThe chttp crate before version 0.3 for Rust contains a use-after-free vulnerability during buffer conversion. This memory safety flaw occurs when memory is accessed after being freed, potentially allowing arbitrary code execution, denial of service, or information disclosure. The vulnerability has a CVSS score of 9.8 indicating critical severity.
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.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
- 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.
-
Check Cargo.lock for chttp crate versionSearch the Cargo.lock file for the chttp crate entry and note the version number listed (e.g., name = "chttp" version = "0.2.5")Affected if The chttp crate version is less than 0.3.0 (such as 0.1.x or 0.2.x)
-
Check Isahc dependency version in Cargo.tomlInspect the Cargo.toml file for the isahc dependency declaration (e.g., isahc = "0.1.2")Affected if Isahc version is exactly 0.1.2
-
Verify chttp is a transitive dependencyRun `cargo tree` or `cargo tree -i chttp` to confirm chttp appears in the dependency tree as a dependency of isahcAffected if The chttp crate appears as a dependency under isahc
-
Confirm code usage of Isahc HTTP clientSearch source files for `use isahc::` or `isahc::` imports and HTTP request/response handling codeAffected if The project actively uses Isahc to make HTTP requests, which triggers the buffer conversion code path where the flaw exists
A system is affected if it uses Isahc version 0.1.2 directly or indirectly pulls in chttp crate versions before 0.3.0 as a 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 · scopedUpdate the chttp crate to version 0.1.3 or later to obtain the patched version. Audit any dependent crates or applications to assess exposure and test thoroughly after updating.
Isahc 0.1.3 (or latest stable)
- Update the Isahc dependency in your Cargo.toml file to version 0.1.3 or later: change `isahc = "0.1.2"` to `isahc = "0.1.3"`
- Run `cargo update` to update the dependency lock file
- Rebuild your project with `cargo build` to ensure the vulnerable version is replaced
- Verify the fix by checking `cargo tree` to confirm Isahc version 0.1.3 or later is being used
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16140 — 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-16140 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