Improper neutralization of special elements used in an LDAP query (LDAP injection) vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (prov modules).
This vulnerability is associated with program files LDAPStoreHelper.
This issue affects BC-JAVA: from 1.74 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.
Weakness
The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat AMQ Broker 7.12.7 | RedHat | bcprov-jdk18on | * |
| Red Hat AMQ Broker 7.13.5 | RedHat | bcprov-jdk18on | * |
| Red Hat Build of Apache Camel 4.14 for Quarkus 3.27 | RedHat | bcprov-jdk18on | * |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | RedHat | bcprov-debug-jdk15on | * |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | RedHat | bcprov-jdk15on | * |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | RedHat | bcprov-jdk18on | * |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | RedHat | bcprov-lts8on | * |
| Red Hat build of Quarkus 3.20.6.SP1 | RedHat | bcprov-jdk18on | * |
| Red Hat build of Quarkus 3.27.3.SP1 | RedHat | bcprov-jdk18on | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-ext-jdk15on | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-ext-jdk18on | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-jdk12 | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-jdk15 | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-jdk15on | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-jdk15to18 | * |
| Red Hat JBoss Enterprise Application Platform 8.1 | RedHat | bcprov-jdk18on | * |
| Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8 | RedHat | eap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el8eap | * |
| Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9 | RedHat | eap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el9eap | * |
| Red Hat OpenShift Dev Spaces 3.28 | RedHat | devspaces/openvsx-rhel9:1779528224 | * |
| Red Hat OpenShift Dev Spaces 3.28 | RedHat | devspaces/pluginregistry-rhel9:1779359423 | * |
| Bouncycastle | Ubuntu | esm-apps/xenial | * |
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.