Skip to content
Fencer Intel
critical 9.8

CVE-2018-1337 json

Credential leak in org.apache.directory.api:apache-ldap-api

published 2018-07-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-cfw5-v7cw-69cw , EUVD-2018-0745

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

Summary

In Apache Directory LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).

Patch / fix

  • maven org.apache.directory.api:apache-ldap-api 1.0.2
  • apache directory_ldap_api 1.0.2
  • apache-directory-api Debian 14, Debian 13, Debian 12 2.1.2-1

debian advisories DEBIAN-CVE-2018-1337

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-2018-1337 updated cvss 6.8

apache-ldap-api: Plaintext Password Disclosure in Secured Channel

  • 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.15% 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 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.directory.api:apache-ldap-api
<1.0.2
1.0.2

Affected products

  • Apache Software Foundation Apache Directory

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.