- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202007-34
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Apache Ant: Multiple vulnerabilities
     Date: July 27, 2020
     Bugs: #723086
       ID: 202007-34

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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.8                  >= 1.10.8

Description
==========
Apache Ant was found to be using multiple insecure temporary files
which may disclose sensitive information or execute code from an unsafe
local location.

Impact
=====
A local attacker could possibly execute arbitrary code with the
privileges of the process, or cause a Denial of Service condition.

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

References
=========
[ 1 ] CVE-2020-1945
      https://nvd.nist.gov/vuln/detail/CVE-2020-1945

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202007-34

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-202007-34: Apache Ant: Multiple vulnerabilities

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

Summary

Apache Ant was found to be using multiple insecure temporary files which may disclose sensitive information or execute code from an unsafe local location.

Resolution

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

References

[ 1 ] CVE-2020-1945 https://nvd.nist.gov/vuln/detail/CVE-2020-1945

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202007-34

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: Multiple vulnerabilities
Date: July 27, 2020
Bugs: #723086
ID: 202007-34

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.8 >= 1.10.8

Impact

===== A local attacker could possibly execute arbitrary code with the privileges of the process, or cause a Denial of Service condition.

Workaround

There is no known workaround at this time.

Related News