CVE-2021-36373 (Medium) detected in ant-1.8.4.jar, ant-1.6.5.jar - autoclosed

[mend-bolt-for-github[bot]]

CVE-2021-36373 - Medium Severity Vulnerability

Vulnerable Libraries - ant-1.8.4.jar, ant-1.6.5.jar

ant-1.8.4.jar

master POM

Path to dependency file: /jetty-jspc-maven-plugin/pom.xml

Path to vulnerable library: /jetty-jspc-maven-plugin/pom.xml

Dependency Hierarchy: - :x: **ant-1.8.4.jar** (Vulnerable Library)

ant-1.6.5.jar

Path to dependency file: /jetty-ant/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/ant/ant/1.6.5/ant-1.6.5.jar

Dependency Hierarchy: - :x: **ant-1.6.5.jar** (Vulnerable Library)

Found in HEAD commit: 58f30216af0fcc8c8d4ee04369790afc5494c144

Found in base branch: main

Vulnerability Details

When reading a specially crafted TAR archive an Apache Ant build can be made to allocate large amounts of memory that finally leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Apache Ant prior to 1.9.16 and 1.10.11 were affected.

Publish Date: 2021-07-14

URL: CVE-2021-36373

CVSS 3 Score Details (5.5)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36373

Release Date: 2021-07-14

Fix Resolution: 1.9.16

---

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #53

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #53

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #53