# CVE-2022-41545: Information disclosure in n/a

> An attacker can intercept administrative credentials via man-in-the-middle attacks because the router uses basic authentication over unencrypted HTTP by default.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-wcpp-7r83-v4gc

## What is CVE-2022-41545?

CVE-2022-41545 is a medium-severity vulnerability in n/a, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The administrative web interface of a Netgear C7800 Router running firmware version 6.01.07 (and possibly others) authenticates users via basic authentication, with an HTTP header containing a base64 value of the plaintext username and password. Because the web server also does not utilize transport security by default, this renders the administrative credentials vulnerable to eavesdropping by an adversary during every authenticated request made by a client to the router over a WLAN, or a LAN, should the adversary be able to perform a man-in-the-middle attack.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2022-41545?

It affects 1 product.


Products: Netgear C7800 Firmware.

## How do I fix CVE-2022-41545?

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

## Is CVE-2022-41545 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41545 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41545 and fix it if it is affected.

What it is: CVE-2022-41545 is a medium-severity vulnerability in n/a, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41545 exists.

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

## Sources

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

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