# CVE-2019-1010299: Information disclosure in Standard Library

> Attackers can read uninitialized memory contents via debug printing of empty VecDeque iterators in the Rust standard library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-1010299, GHSA-q36q-x6v6-cvmp

## What is CVE-2019-1010299?

CVE-2019-1010299 is a medium-severity vulnerability in The Rust Programming Language Standard Library, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Rust Programming Language Standard Library 1.18.0 and later is affected by: CWE-200: Information Exposure. The impact is: Contents of uninitialized memory could be printed to string or to log file. The component is: Debug trait implementation for std::collections::vec_deque::Iter. The attack vector is: The program needs to invoke debug printing for iterator over an empty VecDeque. The fixed version is: 1.30.0, nightly versions after commit b85e4cc8fadaabd41da5b9645c08c68b8f89908d.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-1010299?

It affects 1 product.


Products: Rust-Lang Rust.

## How do I fix CVE-2019-1010299?

Upgrade to a fixed version.

## Is CVE-2019-1010299 being exploited?

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

## Other vulnerabilities in The Rust Programming Language Standard Library

- [CVE-2020-36318](https://insights.sbomify.com/CVE-2020-36318/): Use after free in n/a (critical 9.8)
- [CVE-2018-1000810](https://insights.sbomify.com/CVE-2018-1000810/): Integer overflow in n/a (critical 9.8)
- [CVE-2021-29922](https://insights.sbomify.com/CVE-2021-29922/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-43402](https://insights.sbomify.com/CVE-2024-43402/): Rust OS Command Injection/Argument Injection vulnerability (high 8.2)
- [CVE-2018-1000657](https://insights.sbomify.com/CVE-2018-1000657/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010299 and fix it if it is affected.

What it is: CVE-2019-1010299 is a medium-severity vulnerability in The Rust Programming Language Standard Library, published on 15 Jul 2019. 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-2019-1010299 in the wild and no public exploit code.

Affected product: The Rust Programming Language Standard Library. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2019-1010299/ (Markdown: https://insights.sbomify.com/CVE-2019-1010299/index.md)
```

## Sources

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

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