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. https://www.bouncycastle.org/latest_releases.html
This issue has been addressed in the following products: Red Hat JBoss AMQ Via RHSA-2024:4271 https://access.redhat.com/errata/RHSA-2024:4271
This issue has been addressed in the following products: Red Hat build of Quarkus 3.8.5 Via RHSA-2024:4326 https://access.redhat.com/errata/RHSA-2024:4326