Gentoo: GLSA-202107-52: Apache Velocity: Multiple vulnerabilities |...

Advisories

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202107-52
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Apache Velocity: Multiple vulnerabilities
     Date: July 23, 2021
     Bugs: #775248
       ID: 202107-52

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

Synopsis
========

Multiple vulnerabilities have been found in Apache Velocity, the worst
of which could result in the arbitrary execution of code.

Background
==========

Apache Velocity is a general purpose template engine.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-java/velocity             < 2.3                       >= 2.3 

Description
===========

Multiple vulnerabilities have been discovered in Apache Velocity.
Please review the CVE identifiers referenced below for details.

Impact
======

Please review the referenced CVE identifiers for details.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Apache Velocity users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-java/velocity-2.3"

References
==========

[ 1 ] CVE-2020-13936
      https://nvd.nist.gov/vuln/detail/CVE-2020-13936
[ 2 ] CVE-2020-13959
      https://nvd.nist.gov/vuln/detail/CVE-2020-13959

Availability
============

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

 https://security.gentoo.org/glsa/202107-52

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
[email protected] or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2021 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-202107-52: Apache Velocity: Multiple vulnerabilities

Summary

Multiple vulnerabilities have been discovered in Apache Velocity. Please review the CVE identifiers referenced below for details.

Resolution

All Apache Velocity users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-java/velocity-2.3"

References

[ 1 ] CVE-2020-13936 https://nvd.nist.gov/vuln/detail/CVE-2020-13936 [ 2 ] CVE-2020-13959 https://nvd.nist.gov/vuln/detail/CVE-2020-13959

Availability

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

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 [email protected] or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: Apache Velocity: Multiple vulnerabilities
Date: July 23, 2021
Bugs: #775248
ID: 202107-52

Synopsis

Multiple vulnerabilities have been found in Apache Velocity, the worst of which could result in the arbitrary execution of code.

Background

Apache Velocity is a general purpose template engine.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-java/velocity < 2.3 >= 2.3

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.