org.bouncycastle: Use of Incorrectly-Resolved Name or Reference
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat AMQ Broker 7 | |||
| org.bouncycastle:bcprov-jdk18on | cpe:/a:redhat:amq_broker:7.12 | RHSA-2024:4271 | 2024-07-02T00:00:00Z |
| Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2 | |||
| cpe:/a:redhat:apache_camel_spring_boot:4.4::el6 | RHSA-2024:4884 | 2024-07-25T00:00:00Z | |
| Red Hat build of Quarkus 3.8.5.redhat | |||
| org.bouncycastle/bcprov-jdk18on:1.78.1.redhat-00002 | cpe:/a:redhat:quarkus:3.8::el8 | RHSA-2024:4326 | 2024-07-08T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1414 | 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. |
Github GHSA |
GHSA-4h8f-2wvx-gg5w | Bouncy Castle Java Cryptography API vulnerable to DNS poisoning |
Ubuntu USN |
USN-8108-1 | Bouncy Castle vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.770% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:apache_camel_spring_boot:4.4::el6 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | 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. |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat apache Camel Spring Boot
|
|
| CPEs | cpe:/a:redhat:apache_camel_spring_boot:4.4.1 | |
| Vendors & Products |
Redhat apache Camel Spring Boot
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-297 | |
| Metrics |
cvssV3_1
|
ssvc
|