CVE-2019-15553 : An issue was discovered in the memoffset crate before 0.5.0 for Rust. offset

An issue was discovered in the memoffset crate before 0.5.0 for Rust. offset_of and span_of can cause exposure of uninitialized memory.

Published 2019-08-26 15:15:12

Updated 2020-08-24 17:37:01

Source MITRE

View at NVD, CVE.org

Products affected by CVE-2019-15553

Memoffset Project » Memoffset
Versions before (<) 0.5.0
cpe:2.3:a:memoffset_project:memoffset:*:*:*:*:*:*:*:*
Matching versions

EPSS FAQ

0.15%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 50 %

Percentile, the proportion of vulnerabilities that are scored at or less

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
5.0	MEDIUM	AV:N/AC:L/Au:N/C:P/I:N/A:N	10.0	2.9	NIST
Access Vector: Network Access Complexity: Low Authentication: None Confidentiality Impact: Partial Integrity Impact: None Availability Impact: None
7.5	HIGH	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N	3.9	3.6	NIST
Attack Vector: Network Attack Complexity: Low Privileges Required: None User Interaction: None Scope: Unchanged Confidentiality: High Integrity: None Availability: None

CWE-908 Use of Uninitialized Resource

The product uses or accesses a resource that has not been initialized.

Assigned by: nvd@nist.gov (Primary)

https://rustsec.org/advisories/RUSTSEC-2019-0011.html

RUSTSEC-2019-0011: memoffset: Flaw in offset_of and span_of causes SIGILL, drops uninitialized memory of arbitrary type on panic in client code › RustSec Advisory Database
Third Party Advisory
https://github.com/Gilnaa/memoffset/issues/9#issuecomment-505461490

`offset_of` is unsound · Issue #9 · Gilnaa/memoffset · GitHub
Third Party Advisory

Jump to