# CVE-2020-25573: Access of Uninitialized Pointer in linked-hash-map

> The linked-hash-map crate creates an uninitialized NonNull pointer, potentially causing a crash or undefined behavior in applications using it.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-25573, GHSA-r43h-gmrm-h5c9, RUSTSEC-2020-0026, UBUNTU-CVE-2020-25573

## What is CVE-2020-25573?

CVE-2020-25573 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2020-25573?

3 open source packages ship an affected version, including linked-hash-map. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `linked-hash-map` | crates.io | All versions | 0.5.3 |
| `linked-hash-map` | crates.io | All versions | 0.5.3 |
| `linked-hash-map` | crates.io | From 0.0.0-0 | 0.5.3 |

Products: Linked-Hash-Map Project Linked-Hash-Map.

## How do I fix CVE-2020-25573?

Upgrade linked-hash-map to 0.5.3 or later.

## Is CVE-2020-25573 being exploited?

There is no known exploitation of CVE-2020-25573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25573 and fix it if it is affected.

What it is: CVE-2020-25573 is a critical vulnerability in n/a, published on 14 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25573 in the wild and no public exploit code.

Affected packages and fixed versions:
- linked-hash-map (crates.io): affected all versions; fixed in 0.5.3
- linked-hash-map (crates.io): affected all versions; fixed in 0.5.3
- linked-hash-map (crates.io): affected from 0.0.0-0; fixed in 0.5.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25573/ (Markdown: https://insights.sbomify.com/CVE-2020-25573/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25573
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25573
- OSV: https://osv.dev/vulnerability/CVE-2020-25573

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25573/
Summaries are generated and may contain mistakes; the official description above is the record.