# CVE-2013-4655: Path traversal in n/a

> An attacker can exploit a symlink traversal vulnerability in the Belkin N900 SMB service to read or modify arbitrary files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 13 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jx3f-m8g8-pqmw

## What is CVE-2013-4655?

CVE-2013-4655 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symlink Traversal vulnerability in Belkin N900 due to misconfiguration in the SMB service.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2013-4655?

It affects 1 product.


Products: Belkin N900 Firmware.

## How do I fix CVE-2013-4655?

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

## Is CVE-2013-4655 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3088](https://insights.sbomify.com/CVE-2013-3088/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4655 and fix it if it is affected.

What it is: CVE-2013-4655 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2019. 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-2013-4655 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-2013-4655/ (Markdown: https://insights.sbomify.com/CVE-2013-4655/index.md)
```

## Sources

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

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