|
Vulnerabilities
< Back

CVE-2024-34447

Updated on 03 May 2024

Severity

7.5 High severity

Details

CVSS score
7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CWE ID
Links
NISTCIRCLRHELUbuntu

Overview

About vulnerability

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.

Details

Affected product:
Apache Hive , Bouncy Castle , Eclipse Jetty , OkHttp , Spring , Wildfly , artemis , cas-client-core , cocoon , cryptacular , cxf , directory-server , druid , gradle , itextpdf , java-cas-client , java-opensaml , jets3t , jgit , logging-log4j2 , netty , opensaml-security-api , pulsar , solr , tika , wildfly , ws-wss4j
Affected packages:
tika-fetcher-s3 @ 2.9.1 (+2296 more)
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.

Fixes