Skip to content
Fencer Intel
high 7.5

CVE-2015-3250 json

Exposure of Sensitive Information to an Unauthorized Actor in Apache Directory LDAP API

published 2017-09-07 9 y ago modified 2026-06-17 4 mo ago also GHSA-cx3q-cv6w-mx4h , EUVD-2022-3657

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

Summary

Apache Directory LDAP API before 1.0.0-M31 allows attackers to conduct timing attacks via unspecified vectors.

Patch / fix

  • maven org.apache.directory.api:api-ldap-model 1.0.0-M31
  • apache-directory-api Debian 14, Debian 13, Debian 12 1.0.0~M20-3

debian advisories DEBIAN-CVE-2015-3250

  • apache-directory-api Ubuntu 16.04 LTS 1.0.0~M20-3

ubuntu advisories UBUNTU-CVE-2015-3250

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

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-3250 updated cvss 4.3

apacheds-ldap-client: Timing Attack vulnerability

  • Red Hat All currently supported Red Hat products
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.directory.api:api-ldap-model
<1.0.0-M31
1.0.0-M31

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.