CVE-2024-34447 Affecting apache-nifi package, versions <1.26.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.05% (17th 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-CHAINGUARDLATEST-APACHENIFI-6862011
  • published17 May 2024
  • disclosed3 May 2024

Introduced: 3 May 2024

CVE-2024-34447  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Chainguard apache-nifi to version 1.26.0-r2 or higher.

NVD Description

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

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.

CVSS Scores

version 3.1