# CVE-2020-36513: Use of Uninitialized Resource in acc_reader.

> The acc_reader crate may read from uninitialized memory, potentially exposing sensitive data to attackers.

- **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:** No
- **Published:** 26 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-799f-r78p-gq9c

## What is CVE-2020-36513?

CVE-2020-36513 is a critical vulnerability in n/a, published on 26 Dec 2021. 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 acc_reader crate through 2020-12-27 for Rust. read_up_to may read from uninitialized memory locations.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

2 open source packages ship an affected version, including acc_reader. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `acc_reader` | crates.io | All versions to 2.0.0 | None |
| `acc_reader` | crates.io | All versions to 2.0.0 | None |

Products: Acc Reader Project Acc Reader.

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

No fix has been published for CVE-2020-36513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36513 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36514](https://insights.sbomify.com/CVE-2020-36514/): Use of Uninitialized Resource in acc_reader. (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36513 is a critical vulnerability in n/a, published on 26 Dec 2021. 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-36513 in the wild and no public exploit code.

Affected packages and fixed versions:
- acc_reader (crates.io): affected all versions up to 2.0.0; no fix listed
- acc_reader (crates.io): affected all versions up to 2.0.0; no fix listed

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

## Sources

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

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