CVE-2018-1337GHSA-CFW5-V7CW-69CW
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 connecti
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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).
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache Directory
LDAP API prior to 1.0.2
- org.apache.directory.api:apache-ldap-apiMaven
fixed in 1.0.2
References 8
securityfocus.com
lists.apache.org
- thread.html/d66081195e9a02ee7cc20fb243b60467d1419586eed28297d820768f@<dev.directory.apache.org>
- thread.html/r1a258430d820a90ff9d4558319296cc517ff2252327d7b3546d16749@<jira.kafka.apache.org>
- thread.html/r56b304fb9960c869995efbb31da3b9b7c6d53ee31f7f7048eb80434b@<dev.kafka.apache.org>
- thread.html/r55e74532e7f9e84ecfa56b4e0a50a5fe0ba6f7a76880520e4400b0d7@<jira.kafka.apache.org>
- thread.html/r4da40aa50cfdb2158898f2bc6df81feec1d42c6a06db6537d5cc0496@<jira.kafka.apache.org>
- thread.html/r0e645b3f6ca977dc60b7cec231215c59a9471736c2402c1fef5a0616@<jira.kafka.apache.org>
- thread.html/r1815fb5b0c345f571c740e7a1b48d7477647edd4ffcf9d5321e69446@<dev.kafka.apache.org>