Bouncy Castle Java Cryptography API vulnerable to DNS poisoning
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk18on Maven |
|
|
| org.bouncycastle:bcprov-jdk15to18 Maven |
|
|
| org.bouncycastle:bcprov-jdk14 |
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk18on Maven |
|
|
| org.bouncycastle:bcprov-jdk15to18 Maven |
|
|
| org.bouncycastle:bcprov-jdk14 |
|
|
| org.bouncycastle:bcprov-jdk12 Maven |
|
|
| org.bouncycastle:bctls-fips Maven |
|
|
| org.bouncycastle:bcprov-lts8on Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
|
|
An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.6) and before BC FIPS TLS Java 1.0.19. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be performed against a DNS-resolved IP address in some situations, opening up a possibility of DNS poisoning.
From the CVE record · mitre
BCJSSE can verify a hostname against a DNS-resolved IP address when endpoint identification is enabled and an SSL socket is created without an explicit hostname, as can happen with HttpsURLConnection. This creates a possibility of DNS poisoning; the input does not specify authentication or user-interaction requirements.
Check deployments using org.bouncycastle:bcprov-jdk18on, bcprov-jdk15to18, bcprov-jdk14, bcprov-jdk12, or bcprov-jdk15on versions >=1.61 and <1.78; bctls-fips versions <1.0.19; or bcprov-lts8on versions <2.73.6.