CVE-2019-15553
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 memoffset crate before 0.5.0 for Rust. offset_of and span_of can cause exposure of uninitialized memory.
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 memoffset crate before version 0.5.0 contains unsafe macros (offset_of and span_of) that can cause exposure of uninitialized memory when calculating struct field offsets. These macros fail to properly initialize memory before use, violating memory safety guarantees and potentially leaking sensitive data from the program's memory space.
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.5.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 memoffset version in Cargo.lockOpen the Cargo.lock file in your project root and search for the name = "memoffset" entry. Locate the version field directly below it (e.g., version = "0.4.0").Affected if The version listed is less than 0.5.0 (e.g., 0.4.0, 0.4.1, 0.3.0)
-
Check memoffset version in Cargo.tomlOpen your Cargo.toml file and examine the dependencies or dev-dependencies section for a memoffset entry with a specified version number.Affected if The version specified is less than 0.5.0 (such as ^0.4.0, 0.4.0, or any version below 0.5.0)
-
Search for offset_of macro usageSearch your source code files (particularly .rs files) for the string "offset_of!" including any macro invocations like offset_of!(StructName, field_name).Affected if The offset_of! macro is used in your code and the memoffset version is below 0.5.0
-
Search for span_of macro usageSearch your source code files for the string "span_of!" including any macro invocations like span_of!(StructName, field_name).Affected if The span_of! macro is used in your code and the memoffset version is below 0.5.0
You are affected if your project depends on memoffset crate version below 0.5.0 AND your code uses the offset_of! or span_of! macros.
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.5.0
Upgrade the memoffset crate to version 0.5.0 or later in Cargo.toml to obtain the patched version that properly initializes memory in offset calculations.
- 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-15553 — 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-15553 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