What is CVE-2018-1000134?

CVE-2018-1000134 is a critical-severity security vulnerability in com.unboundid:unboundid-ldapsdk (maven), affecting versions >= 1.1.0, < 4.0.5. It is fixed in 4.0.5.

How severe is CVE-2018-1000134?

CVE-2018-1000134 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.unboundid:unboundid-ldapsdk are affected by CVE-2018-1000134?

com.unboundid:unboundid-ldapsdk (maven) versions >= 1.1.0, < 4.0.5 is affected.

Is there a fix for CVE-2018-1000134?

Yes. CVE-2018-1000134 is fixed in 4.0.5. Upgrade to this version or later.

Is CVE-2018-1000134 exploitable, and should I be worried?

Whether CVE-2018-1000134 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-1000134 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2018-1000134 in com.unboundid:unboundid-ldapsdk

Q: How severe is CVE-2018-1000134?

CVE-2018-1000134 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.unboundid:unboundid-ldapsdk are affected by CVE-2018-1000134?

com.unboundid:unboundid-ldapsdk (maven) versions >= 1.1.0, < 4.0.5 is affected.

Q: Is there a fix for CVE-2018-1000134?

Yes. CVE-2018-1000134 is fixed in 4.0.5. Upgrade to this version or later.

Q: Is CVE-2018-1000134 exploitable, and should I be worried?

Whether CVE-2018-1000134 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-1000134 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-1000134?

Upgrade com.unboundid:unboundid-ldapsdk to 4.0.5 or later.

Summary

Weak Password Requirements in UnboundID LDAP SDK

UnboundID LDAP SDK version from commit 801111d8b5c732266a5dbd4b3bb0b6c7b94d7afb up to commit 8471904a02438c03965d21367890276bc25fa5a6, where the issue was reported and fixed contains an Incorrect Access Control vulnerability in process function in SimpleBindRequest class doesn't check for empty password when running in synchronous mode. The issue can result in ability to impersonate any valid user. This attack appear to be exploitable via Providing valid username and empty password against servers that do not do additional validation as per https://tools.ietf.org/html/rfc4513#section-5.1.1. This vulnerability appears to have been fixed in commit 8471904a02438c03965d21367890276bc25fa5a6.

Impact

CVE-2018-1000134 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.5); upgrading removes the vulnerable code path.

Affected versions

com.unboundid:unboundid-ldapsdk (>= 1.1.0, < 4.0.5)

Security releases

com.unboundid:unboundid-ldapsdk → 4.0.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade com.unboundid:unboundid-ldapsdk to 4.0.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-1000134? CVE-2018-1000134 is a critical-severity security vulnerability in com.unboundid:unboundid-ldapsdk (maven), affecting versions >= 1.1.0, < 4.0.5. It is fixed in 4.0.5.
How severe is CVE-2018-1000134? CVE-2018-1000134 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.unboundid:unboundid-ldapsdk are affected by CVE-2018-1000134? com.unboundid:unboundid-ldapsdk (maven) versions >= 1.1.0, < 4.0.5 is affected.
Is there a fix for CVE-2018-1000134? Yes. CVE-2018-1000134 is fixed in 4.0.5. Upgrade to this version or later.
Is CVE-2018-1000134 exploitable, and should I be worried? Whether CVE-2018-1000134 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-1000134 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-1000134? Upgrade com.unboundid:unboundid-ldapsdk to 4.0.5 or later.