# CVE-2020-19860: Information disclosure in n/a

> An attacker can leak heap memory information by providing a maliciously crafted zone file to the ldns library during verification.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-19860, GHSA-x6hf-28q4-37gq, UBUNTU-CVE-2020-19860

## What is CVE-2020-19860?

CVE-2020-19860 is a medium-severity vulnerability in n/a, published on 21 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

When ldns version 1.7.1 verifies a zone file, the ldns_rr_new_frm_str_internal function has a heap out of bounds read vulnerability. An attacker can leak information on the heap by constructing a zone file payload.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Nlnetlabs Ldns.

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

Upgrade to a fixed version.

## Is CVE-2020-19860 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000231](https://insights.sbomify.com/CVE-2017-1000231/): Use after free in n/a (critical 9.8)
- [CVE-2017-1000232](https://insights.sbomify.com/CVE-2017-1000232/): Use after free in n/a (critical 9.8)
- [CVE-2026-10846](https://insights.sbomify.com/CVE-2026-10846/): Insufficient verification that responses belong to a query (high 8.2)
- [CVE-2020-19861](https://insights.sbomify.com/CVE-2020-19861/): Information disclosure in n/a (high 7.5)
- [CVE-2011-3581](https://insights.sbomify.com/CVE-2011-3581/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-19860 is a medium-severity vulnerability in n/a, published on 21 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-19860 in the wild and no public exploit code.

Affected product: n/a. 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-2020-19860/ (Markdown: https://insights.sbomify.com/CVE-2020-19860/index.md)
```

## Sources

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

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