Alerts This Week
Warning Icon 1 535
Alerts This Week
Warning Icon 1 535

Gentoo: GLSA-202108-48 Normal: Apache HTTP Server Security Vulnerability

gentoo
Calendar Grey July 22, 2021
Dist Gentoo Esm H88
Keep updated on Apache Velocity's various security flaws highlighted in Gentoo's GLSA 202107-52 notice and follow the recommended upgrade steps.
Multiple vulnerabilities have been found in Apache Velocity, the worst of which could result in the arbitrary execution of code.

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

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/velocity < 2.3 >= 2.3

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Related News

Your message here