Use of Incorrectly-Resolved Name or Reference Affecting bouncycastle package, versions <0:1.70-4.amzn2023.0.5


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.77% (51st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-BOUNCYCASTLE-7243359
  • published11 Jun 2024
  • disclosed3 May 2024

Introduced: 3 May 2024

CVE-2024-34447  (opens in a new tab)
CWE-706  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 bouncycastle to version 0:1.70-4.amzn2023.0.5 or higher.
This issue was patched in ALAS2023-2024-636.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bouncycastle package and not the bouncycastle package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1