# CVE-2014-2962: Path traversal in n/a

> Remote attackers can read arbitrary files on Belkin N150 routers via path traversal in the webproc cgi module.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-89f2-h2f5-px5g

## What is CVE-2014-2962?

CVE-2014-2962 is a high-severity path traversal vulnerability in n/a, published on 19 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in the webproc cgi module on the Belkin N150 F9K1009 v1 router with firmware before 1.00.08 allows remote attackers to read arbitrary files via a full pathname in the getpage parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Belkin N150 F9k1009, Belkin N150 F9k1009 Firmware.

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

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

## Is CVE-2014-2962 being exploited?

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

Public exploit code:

- Belkin N150 Router 1.00.08/1.00.09 - Directory Traversal (exploitdb)
- Belkin N150 Router 1.00.08/1.00.09 - Path Traversal (nuclei): http/cves/2014/CVE-2014-2962.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2962 is a high-severity path traversal vulnerability in n/a, published on 19 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-2962 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-2014-2962/ (Markdown: https://insights.sbomify.com/CVE-2014-2962/index.md)
```

## Sources

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

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