An issue was discovered in Bouncy Castle Java Cryptography APIs before BC
1.78. 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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | bouncycastle | < any | UNKNOWN |
ubuntu | 20.04 | noarch | bouncycastle | < any | UNKNOWN |
ubuntu | 22.04 | noarch | bouncycastle | < any | UNKNOWN |
ubuntu | 23.10 | noarch | bouncycastle | < any | UNKNOWN |
ubuntu | 24.04 | noarch | bouncycastle | < any | UNKNOWN |
ubuntu | 16.04 | noarch | bouncycastle | < any | UNKNOWN |