# CVE-2012-6341: Information disclosure in n/a

> Attackers can recover plaintext passwords for the control panel and Wi-Fi encryption from the configuration file of Netgear WGR614 routers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6hv8-2ghp-22qp

## What is CVE-2012-6341?

CVE-2012-6341 is a medium-severity vulnerability in n/a, published on 6 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Information Disclosure vulnerability exists in the my config file in NEtGEAR WGR614 v7 and v9, which could let a malicious user recover all previously used passwords on the device, for both the control panel and WEP/WPA/WPA2, in plaintext. This is a different issue than CVE-2012-6340.

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

## Which versions are affected by CVE-2012-6341?

It affects 2 products.


Products: Netgear Wgr614v7 Firmware, Netgear Wgr614v9 Firmware.

## How do I fix CVE-2012-6341?

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

## Is CVE-2012-6341 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6340](https://insights.sbomify.com/CVE-2012-6340/): Hardcoded credentials in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6341 and fix it if it is affected.

What it is: CVE-2012-6341 is a medium-severity vulnerability in n/a, published on 6 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6341 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-2012-6341/ (Markdown: https://insights.sbomify.com/CVE-2012-6341/index.md)
```

## Sources

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

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