# CVE-2014-2527: Command injection in n/a

> Remote attackers can execute arbitrary commands via double quotes in directory names when KDirStat deletes directories.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c69h-fp8v-vx97

## What is CVE-2014-2527?

CVE-2014-2527 is a medium-severity command injection vulnerability in Opensuse Opensuse, published on 26 Aug 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

kcleanup.cpp in KDirStat 2.7.0 does not properly quote strings when deleting a directory, which allows remote attackers to execute arbitrary commands via a " (double quote) character in the directory name, a different vulnerability than CVE-2014-2528.

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

It affects 2 products.


Products: Kdirstat Project Kdirstat, Opensuse Opensuse.

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

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

## Is CVE-2014-2527 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2014-2528](https://insights.sbomify.com/CVE-2014-2528/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2527 is a medium-severity command injection vulnerability in Opensuse Opensuse, published on 26 Aug 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2527 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2527/ (Markdown: https://insights.sbomify.com/CVE-2014-2527/index.md)
```

## Sources

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

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