CVE-2018-21000 json
Heap overflow or corruption in safe-transmute
published 2018-11-27 7 y ago modified 2026-06-17 4 mo ago also GHSA-2v78-j59h-fmpf , RUSTSEC-2018-0013 , EUVD-2021-1518
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption.
Patch / fix
- crates.io safe-transmute 0.10.1
- safe-transmute_project safe-transmute 0.10.1
Exploit prediction
1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| OSV | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | safe-transmute | >=0.4.0, <0.10.1 |
0.10.1 |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/nabijaczleweli/safe-transmute-rs/pull/36
web, patch, third-party-advisory
-
github.com
/nabijaczleweli/safe-transmute-rs/commit/a134e06d740f9d7c287f74c0af2cd06206774364
web
-
rustsec.org
/advisories/RUSTSEC-2018-0013.html
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-21000
advisory
-
github.com
/nabijaczleweli/safe-transmute-rs
package
-
crates.io
/crates/safe-transmute
package
Sources
- CVE List CVE-2018-21000
- GitHub Advisory GHSA-2v78-j59h-fmpf
- NVD CVE-2018-21000
- OSV RUSTSEC-2018-0013
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.