# CVE-2011-1586: Path traversal in n/a

> Remote attackers can create arbitrary files via path traversal in KGet metalink files, requiring user interaction to open the malicious file.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w8p8-fqqv-v8w8, RHSA-2011:0465

## What is CVE-2011-1586?

CVE-2011-1586 is a medium-severity path traversal vulnerability in n/a, published on 27 Apr 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in the KGetMetalink::File::isValidNameAttr function in ui/metalinkcreator/metalinker.cpp in KGet in KDE SC 4.6.2 and earlier allows remote attackers to create arbitrary files via a .. (dot dot) in the name attribute of a file element in a metalink file.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-1000.

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

## Which versions are affected by CVE-2011-1586?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdenetwork` | Red Hat:enterprise_linux:6::client | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-devel` | Red Hat:enterprise_linux:6::client | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-libs` | Red Hat:enterprise_linux:6::client | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork` | Red Hat:enterprise_linux:6::server | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-devel` | Red Hat:enterprise_linux:6::server | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-libs` | Red Hat:enterprise_linux:6::server | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork` | Red Hat:enterprise_linux:6::workstation | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 7:4.3.4-11.el6_0.1 |
| `kdenetwork-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 7:4.3.4-11.el6_0.1 |

Products: Kde Kde Sc.

## How do I fix CVE-2011-1586?

Upgrade to a fixed version.

## Is CVE-2011-1586 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0436](https://insights.sbomify.com/CVE-2010-0436/): Race condition in n/a (medium 6.9)
- [CVE-2010-0923](https://insights.sbomify.com/CVE-2010-0923/): Race condition in n/a (medium 6.9)
- [CVE-2010-2575](https://insights.sbomify.com/CVE-2010-2575/): Memory corruption in n/a (medium 6.8)
- [CVE-2010-1511](https://insights.sbomify.com/CVE-2010-1511/): Path traversal in n/a (medium 6.4)
- [CVE-2010-1000](https://insights.sbomify.com/CVE-2010-1000/): Path traversal in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1586 and fix it if it is affected.

What it is: CVE-2011-1586 is a medium-severity path traversal vulnerability in n/a, published on 27 Apr 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-1586 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-2011-1586/ (Markdown: https://insights.sbomify.com/CVE-2011-1586/index.md)
```

## Sources

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

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