hdfs-fixture-3.0.0-SNAPSHOT: 1 vulnerabilities (highest severity is: 8.9)

[mend-for-github-com]

Vulnerable Library - hdfs-fixture-3.0.0-SNAPSHOT

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar

Found in HEAD commit: 45e73c43e36926a8a03b094ec1ea254f5de91beb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (hdfs-fixture version)	Remediation Possible**
CVE-2024-25638	High	8.9	dnsjava-3.4.0.jar	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-25638

Vulnerable Library - dnsjava-3.4.0.jar

dnsjava is an implementation of DNS in Java. It supports all defined record types (including the DNSSEC types), and unknown types. It can be used for queries, zone transfers, and dynamic updates. It includes a cache which can be used by clients, and a minimal implementation of a server. It supports TSIG authenticated messages, partial DNSSEC verification, and EDNS0.

Library home page: https://github.com/dnsjava/dnsjava

Path to dependency file: /build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/dnsjava/dnsjava/3.4.0/a214858bba6ddc017a3c2fd5d17f0ee359770dad/dnsjava-3.4.0.jar

Dependency Hierarchy:

• hdfs-fixture-3.0.0-SNAPSHOT (Root Library)
  • hadoop-minicluster-3.4.0.jar
    • hadoop-yarn-server-tests-3.4.0.jar
      • hadoop-yarn-server-nodemanager-3.4.0.jar
        • hadoop-registry-3.4.0.jar
          • ❌ dnsjava-3.4.0.jar (Vulnerable Library)

Found in HEAD commit: 45e73c43e36926a8a03b094ec1ea254f5de91beb

Found in base branch: main

Vulnerability Details

dnsjava is an implementation of DNS in Java. Records in DNS replies are not checked for their relevance to the query, allowing an attacker to respond with RRs from different zones. This vulnerability is fixed in 3.6.0.

Publish Date: 2024-07-22

URL: CVE-2024-25638

CVSS 3 Score Details (8.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-cfxw-4h78-h7fw

Release Date: 2024-07-22

Fix Resolution: dnsjava:dnsjava:3.6.0

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[dblock]

cc: @varun-lodaya @gbbafna

[derek-ho]

I raised a draft PR here: #15173, but it seems like the whitesource check failed. Can a maintainer re-run it/review the PR to see if it follows appropriate conventions? CC @varun-lodaya @reta

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.