GHSA-hr8g-6v94-x4m9 Bouncy Castle For Java LDAP injection vulnerability

• Maven org.bouncycastle:bcprov-jdk18on: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-jdk15to18: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-jdk14: >= 1.49, < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-ext-jdk14: >= 1.49, < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-ext-jdk15to18: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-ext-jdk18on: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-debug-jdk14: >= 1.49, < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-debug-jdk15to18: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-debug-jdk18on: < 1.74 → fixed in 1.74 • Maven org.bouncycastle:bcprov-jdk15on: >= 1.49, <= 1.70 (no fix yet) • Maven org.bouncycastle:bcprov-ext-jdk15on: >= 1.49, <= 1.70 (no fix yet) • Maven org.bouncycastle:bcprov-debug-jdk15on: >= 1.49, <= 1.70 (no fix yet)

Bouncy Castle provides the `X509LDAPCertStoreSpi.java` class which can be used in conjunction with the CertPath API for validating certificate paths. Pre-1.73 the implementation did not check the X.500 name of any certificate, subject, or issuer being passed in for LDAP wild cards, meaning the presence of a wild car may lead to Information Disclosure. A potential attack would be to generate a self-signed certificate with a subject name that contains special characters, e.g: `CN=Subject*)(objectclass=`. This will be included into the filter and provides the attacker ability to specify additional attributes in the search query. This can be exploited as a blind LDAP injection: an attacker can enumerate valid attribute values using the boolean blind injection technique. The exploitation depends on the structure of the target LDAP directory, as well as what kind of errors are exposed to the user. Changes to the `X509LDAPCertStoreSpi.java` class add the additional checking of any X.500 name used to correctly escape wild card characters.