# CVE-2021-45603: Information disclosure in n/a

> A UPnP request reveals the device serial number, enabling password reset and potential account takeover on NETGEAR routers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:L/A:L/C:H/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qx9q-hrrj-rj5g

## What is CVE-2021-45603?

CVE-2021-45603 is a medium-severity vulnerability in Netgear D7800 Firmware, published on 26 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by disclosure of sensitive information. A UPnP request reveals a device's serial number, which can be used for a password reset. This affects D7800 before 1.0.1.66, EX2700 before 1.0.1.68, WN3000RPv2 before 1.0.0.90, WN3000RPv3 before 1.0.2.100, LBR1020 before 2.6.5.20, LBR20 before 2.6.5.32, R6700AX before 1.0.10.110, R7800 before 1.0.2.86, R8900 before 1.0.5.38, R9000 before 1.0.5.38, RAX10 before 1.0.10.110, RAX120v1 before 1.2.3.28, RAX120v2 before 1.2.3.28, RAX70 before 1.0.10.110, RAX78 before 1.0.10.110, XR450 before 2.3.2.130, XR500 before 2.3.2.130, and XR700 before 1.0.1.46.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-45603?

It affects 18 products.


Products: Netgear D7800 Firmware, Netgear Ex2700 Firmware, Netgear Lbr1020 Firmware, Netgear Lbr20 Firmware, Netgear R6700ax Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rax10 Firmware, Netgear Rax120v1 Firmware, Netgear Rax120v2 Firmware, Netgear Rax70 Firmware, Netgear Rax78 Firmware, Netgear Wn3000rpv2 Firmware, Netgear Wn3000rpv3 Firmware, Netgear Xr450 Firmware, Netgear Xr500 Firmware, Netgear Xr700 Firmware.

## How do I fix CVE-2021-45603?

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

## Is CVE-2021-45603 being exploited?

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

## Other vulnerabilities in Netgear D7800 Firmware

- [CVE-2021-45618](https://insights.sbomify.com/CVE-2021-45618/): Command injection in n/a (critical 9.6)
- [CVE-2021-34947](https://insights.sbomify.com/CVE-2021-34947/): NETGEAR R7800 net-cgi Out-Of-Bounds Write Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-27641](https://insights.sbomify.com/CVE-2022-27641/): Integer overflow in R6700v3 (high 8.8)
- [CVE-2020-26909](https://insights.sbomify.com/CVE-2020-26909/): Command injection in n/a (high 8.8)
- [CVE-2018-21202](https://insights.sbomify.com/CVE-2018-21202/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45603 and fix it if it is affected.

What it is: CVE-2021-45603 is a medium-severity vulnerability in Netgear D7800 Firmware, published on 26 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-45603 in the wild and no public exploit code.

Affected product: Netgear D7800 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-2021-45603/ (Markdown: https://insights.sbomify.com/CVE-2021-45603/index.md)
```

## Sources

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

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