dbcve.org
Directory Ldap ApiApplication · Apache

CVE-2018-1337

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-10
Fix available
A fix is available. Upgrade to 1.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A race condition in Apache Directory LDAP API's connection pooling allows another thread to reuse a pooled connection before the TLS handshake completes. If credentials were sent in a BIND request on that connection before it was returned to the pool, those credentials can be leaked to another thread using the same connection.

MitigationUpgrade Apache Directory LDAP API to version 1.0.2 or later, which fixes the SSL Filter setup race condition.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Directory Ldap ApiApplication
Affected:< 1.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Directory LDAP API usage
    Inspect application dependencies (Maven pom.xml, Gradle build files, or JAR manifest) for org.apache.directory.studio:org.apache.directory.studio.library or org.apache.directory:ldap-api dependency. Search classpath for org.apache.directory.ldap.api classes.
    Affected if The Apache Directory LDAP API library is present in the application dependencies or classpath
  2. Determine installed library version
    Locate the Apache Directory LDAP API JAR file and check its version in the filename or MANIFEST.MF, or query the dependency management system for the exact version number.
    Affected if The version is lower than 1.0.2 (for example, 1.0.0, 0.9.x, or any version string not >= 1.0.2)
  3. Verify connection pooling is enabled
    Search application configuration files and Java code for LdapConnectionConfig or pool-related settings. Look for DefaultLdapConnectionPool or similar pool instantiation. Check for pool configuration objects being used.
    Affected if The application uses DefaultLdapConnectionPool or configures LDAP connection pooling in code or configuration
  4. Confirm TLS/SSL is used with pooled connections
    Examine LdapConnectionConfig for setSslProtocol or setUseSsl(true) calls. Check if StartTLS or LDAPS is configured. Review network traffic or logs for SSL/TLS handshake patterns on LDAP connections.
    Affected if SSL/TLS is enabled on LDAP connections that use the connection pool

A user is affected if they use Apache Directory LDAP API version below 1.0.2 AND have connection pooling enabled with TLS/SSL, as this creates the race condition window where credentials could leak between threads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.2 or later
Fixed in 1.0.2
Interim mitigation

Upgrade Apache Directory LDAP API to version 1.0.2 or later, which fixes the SSL Filter setup race condition.

Recommended fix High confidence

1.0.2 (or latest stable 1.x release)

  1. Identify the current version of Apache Directory LDAP API dependency in your project (check pom.xml, build.gradle, or equivalent dependency management file)
  2. Update the Apache Directory LDAP API dependency to version 1.0.2 or later. For Maven, change the version in pom.xml: <groupId>org.apache.directory.api</groupId><artifactId>api-ldap</artifactId><version>1.0.2</version>
  3. If using a parent POM or dependency management, ensure the updated version is propagated to all dependent modules
  4. Rebuild the application with the updated dependency
  5. Restart any services or applications using this library to ensure the new version is loaded
  6. Test that LDAP connections with TLS/SSL work correctly, particularly testing BIND operations over secure connections
  7. Verify that concurrent connection pool usage no longer exposes credentials or other request data between threads
Caveat Minimal risk - this is a bug fix for a security vulnerability; review release notes for any API changes if upgrading beyond 1.0.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directory Ldap Api Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1337 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data