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

[mend-for-github-com]

Vulnerable Library - hdfs-fixture-3.0.0-SNAPSHOT

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar,/tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar,/tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar

Found in HEAD commit: 45e73c43e36926a8a03b094ec1ea254f5de91beb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (hdfs-fixture version)	Remediation Possible**
CVE-2024-6763	Low	3.7	jetty-http-9.4.55.v20240627.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-6763

Vulnerable Library - jetty-http-9.4.55.v20240627.jar

Library home page: https://webtide.com

Path to dependency file: /build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar,/tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar,/tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-http/9.4.55.v20240627/ef807d867948042293487c025f953fb8e7d77622/jetty-http-9.4.55.v20240627.jar

Dependency Hierarchy:

• hdfs-fixture-3.0.0-SNAPSHOT (Root Library)
  • javax-websocket-server-impl-9.4.55.v20240627.jar
    • websocket-server-9.4.55.v20240627.jar
      • ❌ jetty-http-9.4.55.v20240627.jar (Vulnerable Library)

Found in HEAD commit: 45e73c43e36926a8a03b094ec1ea254f5de91beb

Found in base branch: main

Vulnerability Details

Eclipse Jetty is a lightweight, highly scalable, Java-based web server and Servlet engine . It includes a utility class, HttpURI, for URI/URL parsing. The HttpURI class does insufficient validation on the authority segment of a URI. However the behaviour of HttpURI differs from the common browsers in how it handles a URI that would be considered invalid if fully validated against the RRC. Specifically HttpURI and the browser may differ on the value of the host extracted from an invalid URI and thus a combination of Jetty and a vulnerable browser may be vulnerable to a open redirect attack or to a SSRF attack if the URI is used after passing validation checks.

Publish Date: 2024-10-14

URL: CVE-2024-6763

CVSS 3 Score Details (3.7)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-qh8g-58pp-2wxh

Release Date: 2024-10-14

Fix Resolution: org.eclipse.jetty:jetty-http:12.0.12;org.eclipse.jetty:jetty-server:12.0.12

[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 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.

[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.