CVE-2019-15550
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 simd-json crate before 0.1.15 for Rust. There is an out-of-bounds read and an incorrect crossing of a page boundary.
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 simd-json Rust crate versions before 0.1.15 contain an out-of-bounds read vulnerability that can incorrectly handle page boundary crossings during JSON parsing. This memory safety flaw allows reading beyond allocated buffer boundaries, potentially exposing sensitive memory contents or causing denial of service through crashes.
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.13, < 0.1.15CVSS 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.1/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 simd-json dependency in your projectExamine your project's Cargo.toml file and search for 'simd-json' under the [dependencies] section. Also check Cargo.lock for the resolved version entry.Affected if The listed version is greater than 0.1.13 but less than 0.1.15 (for example, 0.1.14, 0.1.14.0, or any 0.1.x version in that range).
-
Query the installed crate version programmaticallyRun 'cargo tree -p simd-json' in your project directory to display the exact version of the simd-json crate as it is currently resolved and built.Affected if The output shows a version between 0.1.14 and 0.1.14.9, or any version greater than 0.1.13 but below 0.1.15.
-
Verify JSON parsing is performed using simd-jsonSearch your source code for imports and usage of simd-json parsing functions (such as 'parse', 'parse_into', or similar APIs from the crate).Affected if Your code directly calls simd-json parsing methods to process untrusted or any JSON input, making the out-of-bounds read vulnerability reachable.
-
Check for indirect dependency usageRun 'cargo tree -i simd-json' to see which of your direct dependencies depend on simd-json, since it may be a transitive dependency not explicitly listed in your Cargo.toml.Affected if A transitive dependency pulls in a vulnerable simd-json version (greater than 0.1.13 and less than 0.1.15) and your application invokes the JSON parsing functionality of that dependency.
You are affected if your project directly or indirectly uses simd-json version 0.1.14 or any version greater than 0.1.13 but below 0.1.15 for JSON parsing.
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.1.15
Upgrade the simd-json dependency to version 0.1.15 or later in Cargo.toml, then rebuild and thoroughly test JSON parsing functionality to ensure correct behavior.
- Consultation1.0 h
- Implementation1.0 h
- Testing4.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,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15550 — 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-15550 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