glsa-201612-05.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201612-05">
  <title>Pygments: Arbitrary code execution</title>
  <synopsis>Pygments is vulnerable to remote code execution if an attacker is
    allowed to specify the font name. 
  </synopsis>
  <product type="ebuild">pygments</product>
  <announced>2016-12-04</announced>
  <revised>2016-12-04: 1</revised>
  <bug>564478</bug>
  <access>remote</access>
  <affected>
    <package name="dev-python/pygments" auto="yes" arch="*">
      <unaffected range="ge">2.0.2-r1</unaffected>
      <vulnerable range="lt">2.0.2-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>Pygments is a generic syntax highlighter suitable for use in code
      hosting, forums, wikis or other applications that need to prettify source
      code.
    </p>
  </background>
  <description>
    <p>A vulnerability in FontManager’s _get_nix_font_path function allows
      shell metacharacters to be passed in a font name.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could possibly execute arbitrary code with the
      privileges of the process.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All Pygments users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=dev-python/pygments-2.0.2-r1"
    </code>
  </resolution>
  <references>
    <uri link="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8557">
      CVE-2015-8557
    </uri>
  </references>
  <metadata tag="requester" timestamp="2015-12-08T00:25:56Z">
    BlueKnight
  </metadata>
  <metadata tag="submitter" timestamp="2016-12-04T06:50:34Z">whissi</metadata>
</glsa>