Linux Security Advisory                           GLSA 202011-18
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.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.

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

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

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.

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

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.

License
======
Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202011-18: Apache Ant: Insecure temporary file

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

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

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.

Related News