# CVE-2002-2355: Information disclosure in n/a

> Local users can read cleartext credentials and configuration data from Netgear FM114P firmware when backup is enabled.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:C/I:N/A: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:** 29 Oct 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v2w7-2hcc-x4jg

## What is CVE-2002-2355?

CVE-2002-2355 is a high-severity vulnerability in n/a, published on 29 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Netgear FM114P firmware 1.3 wireless firewall, when configured to backup configuration information, stores DDNS (DynDNS) user name and password, MAC address filtering table and possibly other information in cleartext, which could allow local users to obtain sensitive information.

Weakness: CWE-255

## Which versions are affected by CVE-2002-2355?

It affects 1 product.


Products: Netgear Fm114p.

## How do I fix CVE-2002-2355?

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

## Is CVE-2002-2355 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2354](https://insights.sbomify.com/CVE-2002-2354/): Denial of service in n/a (high 7.8)
- [CVE-2002-1877](https://insights.sbomify.com/CVE-2002-1877/): Security feature bypass in n/a (high 7.5)
- [CVE-2003-1427](https://insights.sbomify.com/CVE-2003-1427/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2355 and fix it if it is affected.

What it is: CVE-2002-2355 is a high-severity vulnerability in n/a, published on 29 Oct 2007. 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-2002-2355 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-2002-2355/ (Markdown: https://insights.sbomify.com/CVE-2002-2355/index.md)
```

## Sources

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

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