WS-2023-0236 (Low) detected in jetty-xml-11.0.12.jar - autoclosed

[mend-for-github-com]

WS-2023-0236 - Low Severity Vulnerability

Vulnerable Library - jetty-xml-11.0.12.jar

The jetty xml utilities.

Library home page: https://eclipse.org/jetty

Path to dependency file: /data-prepper-plugins/s3-source/build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-xml/11.0.12/c47d1eb5032141b7ebd5f83f317a07a4fcad6612/jetty-xml-11.0.12.jar

Dependency Hierarchy:

• wiremock-3.0.0-beta-8.jar (Root Library)
  • jetty-webapp-11.0.12.jar
    • ❌ jetty-xml-11.0.12.jar (Vulnerable Library)

Found in HEAD commit: 8bb96ddcf23859e0e7b55c3a9add5d77eddbccb0

Found in base branch: main

Vulnerability Details

XmlParser is vulnerable to XML external entity (XXE) vulnerability.
XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit this vulnerability in order to achieve SSRF or cause a denial of service. One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the WAR includes a malicious web.xml. The vulnerability is patched in versions 10.0.16, 11.0.16, and 12.0.0.

Publish Date: 2023-07-10

URL: WS-2023-0236

CVSS 3 Score Details (3.9)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-58qw-p7qm-5rvh

Release Date: 2023-07-10

Fix Resolution: org.eclipse.jetty:jetty-xml:10.0.16,11.0.16,12.0.0

[dlvenable]

This vulnerability appears to be coming from hadoop-common, however we don't use Hadoop as a server - just for parsing. Can we exclude the Jetty dependencies from this project?

[asifsmohammed]

Excluding jetty from hadoop-common is not fixing it, trying to manually use the latest version.

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

[dlvenable]

This was fixed in 2.5.0, but reintroduced in the main branch when #3313 was merged.

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