org.apache.ant:ant@1.10.8 vulnerabilities
-
latest version
1.10.14
-
latest non vulnerable version
-
first published
17 years ago
-
latest version published
8 months ago
-
licenses detected
- [0,)
-
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.ant:ant package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.| Vulnerability | Vulnerable Version |
|---|---|
org.apache.ant:ant is a software tool for automating software build processes which originated from the Apache Tomcat project in early 2000. Affected versions of this package are vulnerable to Denial of Service (DoS). When reading a specially crafted ZIP archive, or a derived format, an Apache Ant build can be made to allocate large amounts of memory that leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Commonly used derived formats of ZIP archives include JAR files. How to fix Denial of Service (DoS)? Upgrade |
[,1.9.16)
[1.10.0,1.10.11)
|
org.apache.ant:ant is a software tool for automating software build processes which originated from the Apache Tomcat project in early 2000. Affected versions of this package are vulnerable to Denial of Service (DoS). 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. How to fix Denial of Service (DoS)? Upgrade |
[1.9.0,1.9.16)
[1.10.0,1.10.11)
|
org.apache.ant:ant is a software tool for automating software build processes which originated from the Apache Tomcat project in early 2000. Affected versions of this package are vulnerable to Arbitrary Code Injection. 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. How to fix Arbitrary Code Injection? Upgrade |
[,1.10.9)
|