Skip to content
Fencer Intel
critical 9.8

CVE-2020-25573 json

Access of Uninitialized Pointer in linked-hash-map

published 6y ago modified 4mo ago also GHSA-r43h-gmrm-h5c9 , RUSTSEC-2020-0026 , EUVD-2021-1854

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.

Patch / fix

  • crates.io linked-hash-map 0.5.3
  • linked-hash-map_project linked-hash-map 0.5.3
  • rust-linked-hash-map Debian 14, Debian 13, Debian 12 0.5.4-1

debian advisories DEBIAN-CVE-2020-25573

Is CVE-2020-25573 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.83% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/contain-rs/linked-hash-map/pull/100 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/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
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/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 linked-hash-map
<0.5.3
>=0.0.0-0, <0.5.3
0.5.3

Classification

Weakness
  • CWE-824 Access of Uninitialized Pointer

References

Sources

Fencer Intel 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.