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

> An attacker can exploit SMB symlink traversal in D-Link DIR-865L routers to access or modify files outside the intended share.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-27mm-4p4v-5qpj

## What is CVE-2013-4855?

CVE-2013-4855 is a high-severity path traversal vulnerability in n/a, published on 25 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DIR-865L has SMB Symlink Traversal due to misconfiguration in the SMB service allowing symbolic links to be created to locations outside of the Samba share.

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

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

It affects 1 product.


Products: Dlink Dir-865l Firmware.

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

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

## Is CVE-2013-4855 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4857](https://insights.sbomify.com/CVE-2013-4857/): Path traversal in n/a (critical 9.8)
- [CVE-2020-13782](https://insights.sbomify.com/CVE-2020-13782/): Command injection in n/a (high 8.8)
- [CVE-2020-13786](https://insights.sbomify.com/CVE-2020-13786/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-13783](https://insights.sbomify.com/CVE-2020-13783/): Information disclosure in n/a (high 7.5)
- [CVE-2020-13784](https://insights.sbomify.com/CVE-2020-13784/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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