# CVE-2015-5349: Apache Directory Studio Command Injection

> Attackers can execute arbitrary commands via crafted LDAP entries exported to CSV and imported into spreadsheets in Apache Directory Studio.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p9qj-4rjp-j3w9

## What is CVE-2015-5349?

CVE-2015-5349 is a high-severity command injection vulnerability in n/a, published on 11 Apr 2016. 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

The CSV export in Apache LDAP Studio and Apache Directory Studio before 2.0.0-M10 does not properly escape field values, which might allow attackers to execute arbitrary commands by leveraging a crafted LDAP entry that is interpreted as a formula when imported into a spreadsheet.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2015-5349?

2 open source packages ship an affected version, including org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core` | Maven | All versions | 2.0.0.v20151221-M10 |
| `org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core` | Maven | All versions | 2.0.0.v20151221-M10 |

Products: Apache Directory Studio, Apache Ldap Studio.

## How do I fix CVE-2015-5349?

Upgrade org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core to 2.0.0.v20151221-M10 or later.

## Is CVE-2015-5349 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33900](https://insights.sbomify.com/CVE-2021-33900/): StartTLS and SASL confidentiality protection bypass (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5349 and fix it if it is affected.

What it is: CVE-2015-5349 is a high-severity command injection vulnerability in n/a, published on 11 Apr 2016. 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-2015-5349 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core (Maven): affected all versions; fixed in 2.0.0.v20151221-M10
- org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core (Maven): affected all versions; fixed in 2.0.0.v20151221-M10

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-2015-5349/ (Markdown: https://insights.sbomify.com/CVE-2015-5349/index.md)
```

## Sources

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

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