GHSA-4h8f-2wvx-gg5w Bouncy Castle Java Cryptography API vulnerable to DNS poisoning

• Maven org.bouncycastle:bcprov-jdk18on: >= 1.61, < 1.78 → fixed in 1.78 • Maven org.bouncycastle:bcprov-jdk15to18: >= 1.61, < 1.78 → fixed in 1.78 • Maven org.bouncycastle:bcprov-jdk14: >= 1.61, < 1.78 → fixed in 1.78 • Maven org.bouncycastle:bcprov-jdk12: >= 1.61, < 1.78 → fixed in 1.78 • Maven org.bouncycastle:bctls-fips: < 1.0.19 → fixed in 1.0.19 • Maven org.bouncycastle:bcprov-lts8on: < 2.73.6 → fixed in 2.73.6 • Maven org.bouncycastle:bcprov-jdk15on: >= 1.61, < 1.78 → fixed in 1.78

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.