Alerts This Week
Warning Icon 1 666
Alerts This Week
Warning Icon 1 666

Gentoo: GLSA-201612-05 Moderate: Pygments Remote Code Execution Risk

gentoo
Calendar Grey December 4, 2016
Dist Gentoo Esm H88
The Gentoo Linux Security Advisory GLSA 202201-03 highlights a risk in Pygments that could enable unauthorized remote code execution.
Pygments is vulnerable to remote code execution if an attacker is allowed to specify the font name.

Summary

A vulnerability in FontManager's _get_nix_font_path function allows shell metacharacters to be passed in a font name.

Resolution

All Pygments users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-python/pygments-2.0.2-r1"

References

[ 1 ] CVE-2015-8557 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8557

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201612-05
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: Pygments: Arbitrary code execution
Date: December 04, 2016
Bugs: #564478
ID: 201612-05

Synopsis

Pygments is vulnerable to remote code execution if an attacker is allowed to specify the font name.

Background

Pygments is a generic syntax highlighter suitable for use in code hosting, forums, wikis or other applications that need to prettify source code.

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-python/pygments < 2.0.2-r1 >= 2.0.2-r1

Impact

===== A remote attacker could possibly execute arbitrary code with the privileges of the process.

Workaround

There is no known workaround at this time.

Related News

Your message here