CVE-2020-11979 (High) detected in ant-1.8.4.jar, ant-1.6.5.jar

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

CVE-2020-11979 - High 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: /home/wss-scanner/.m2/repository/org/apache/ant/ant/1.8.4/ant-1.8.4.jar

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: e4f77a76743d4b8fa6fe69cb1085577284ceb3e1

Found in base branch: master

Vulnerability Details

As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.

Publish Date: 2020-10-01

URL: CVE-2020-11979

CVSS 3 Score Details (7.5)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://ant.apache.org/security.html

Release Date: 2020-10-01

Fix Resolution: 1.10.9

---

Step up your Open Source Security Game with Mend here

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

:heavy_check_mark: 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-bolt-for-github[bot]]

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