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

> Attackers can disclose administrative credentials on NETGEAR RAX35, RAX38, and RAX40 routers, potentially leading to full device compromise.

- **Severity:** High 7.6 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:L/PR:N/S:U/UI:R`)
- **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:** No
- **Published:** 26 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2q72-x7j8-g7gh

## What is CVE-2021-45493?

CVE-2021-45493 is a high-severity vulnerability in n/a, published on 26 Dec 2021. 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

Certain NETGEAR devices are affected by disclosure of administrative credentials. This affects RAX35 before 1.0.4.102, RAX38 before 1.0.4.102, and RAX40 before 1.0.4.102.

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

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

It affects 3 products.


Products: Netgear Rax35 Firmware, Netgear Rax38 Firmware, Netgear Rax40 Firmware.

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

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

## Is CVE-2021-45493 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41449](https://insights.sbomify.com/CVE-2021-41449/): Path traversal in n/a (high 7.1)
- [CVE-2021-38526](https://insights.sbomify.com/CVE-2021-38526/): Memory corruption in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45493 is a high-severity vulnerability in n/a, published on 26 Dec 2021. 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-2021-45493 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-2021-45493/ (Markdown: https://insights.sbomify.com/CVE-2021-45493/index.md)
```

## Sources

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

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