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

> Attackers can obtain TLS private keys from NETGEAR routers, enabling decryption of traffic and impersonation of the device.

- **Severity:** High 7.5 (`CVSS:3.0/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hpc6-jf76-gpqr

## What is CVE-2020-11792?

CVE-2020-11792 is a high-severity vulnerability in Netgear R8900 Firmware, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR R8900, R9000, RAX120, and XR700 devices before 2020-01-20 are affected by Transport Layer Security (TLS) certificate private key disclosure.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 4 products.


Products: Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rax120 Firmware, Netgear Xr700 Firmware.

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

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

## Is CVE-2020-11792 being exploited?

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

## Other vulnerabilities in Netgear R8900 Firmware

- [CVE-2019-20650](https://insights.sbomify.com/CVE-2019-20650/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11792 is a high-severity vulnerability in Netgear R8900 Firmware, published on 15 Apr 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-11792 in the wild and no public exploit code.

Affected product: Netgear R8900 Firmware. 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-11792/ (Markdown: https://insights.sbomify.com/CVE-2020-11792/index.md)
```

## Sources

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

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