# CVE-2014-2969: Hardcoded credentials in n/a

> Remote attackers can exploit a hardcoded debug password to upload firmware and execute arbitrary code on NETGEAR Prosafe Plus switches.

- **Severity:** High 8.3 (`AV:A/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h3hf-hqw2-hx35

## What is CVE-2014-2969?

CVE-2014-2969 is a high-severity vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR GS108PE Prosafe Plus switches with firmware 1.2.0.5 have a hardcoded password of debugpassword for the ntgruser account, which allows remote attackers to upload firmware or read or modify memory contents, and consequently execute arbitrary code, via a request to (1) produce_burn.cgi, (2) register_debug.cgi, or (3) bootcode_update.cgi.

Weakness: CWE-255

## Which versions are affected by CVE-2014-2969?

It affects 2 products.


Products: Netgear Gs108pe, Netgear Gs108pe Firmware.

## How do I fix CVE-2014-2969?

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

## Is CVE-2014-2969 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2969 and fix it if it is affected.

What it is: CVE-2014-2969 is a high-severity vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2969 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-2014-2969/ (Markdown: https://insights.sbomify.com/CVE-2014-2969/index.md)
```

## Sources

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

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