Alerts This Week
Warning Icon 1 640
Alerts This Week
Warning Icon 1 640

Gentoo: GLSA-202011-18 Normal Severity: Apache Ant Symlink Attack Risk

gentoo
Calendar Grey November 15, 2020
Dist Gentoo Esm H88
Apache Ant weaknesses revealed insecure files, enabling local exploitation. Implement updates to reduce risks in Gentoo platforms.
Apache Ant uses various insecure temporary files possibly allowing local code execution.

Summary

A previous fix for a security vulnerability involving insecure temporary files has been found to be incomplete.

Resolution

All Apache Ant users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-java/ant-1.10.9"

References

[ 1 ] CVE-2020-11979 https://nvd.nist.gov/vuln/detail/CVE-2020-11979 [ 2 ] GLSA-202007-34 https://security.gentoo.org/glsa/202007-34

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202011-18
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Apache Ant: Insecure temporary file
Date: November 16, 2020
Bugs: #745768
ID: 202011-18

Synopsis

Apache Ant uses various insecure temporary files possibly allowing local code execution.

Background

Ant is a Java-based build tool similar to ‘make’ that uses XML configuration files.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-java/ant < 1.10.9 >= 1.10.9

Impact

===== A local attacker could perform symlink attacks to overwrite arbitrary files with the privileges of the user running the application.

Workaround

There is no known workaround at this time.

Your message here