Skip to content
Fencer Intel
high 7.8

CVE-2015-5349 json

Apache Directory Studio Command Injection

published 2016-04-11 10 y ago modified 2026-06-17 4 mo ago also GHSA-p9qj-4rjp-j3w9 , EUVD-2022-4725

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core 2.0.0.v20151221-M10

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-5349 updated cvss 7.8

apache-directory: command injection via crafted LDAP entry that is interpreted as a formula when imported into a spreadsheet

  • Red Hat build of OpenJDK 11 javax.inject
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
GitHub 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.directory.studio:org.apache.directory.studio.ldapbrowser.core
<2.0.0.v20151221-M10
2.0.0.v20151221-M10

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.