summaryrefslogtreecommitdiff
blob: f07fd9462f9e10b12ac31f76a13a8bed60cbad17 (plain)
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
56
57
58
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201201-08">
  <title>FontForge: User-assisted execution of arbitrary code</title>
  <synopsis>A stack-based buffer overflow flaw in FontForge could result in
    execution of arbitrary code or a Denial of Service.
  </synopsis>
  <product type="ebuild">FontForge</product>
  <announced>2012-01-23</announced>
  <revised count="1">2012-01-23</revised>
  <bug>386293</bug>
  <access>remote</access>
  <affected>
    <package name="media-gfx/fontforge" auto="yes" arch="*">
      <unaffected range="ge">20110222-r1</unaffected>
      <vulnerable range="lt">20110222-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>FontForge is a PostScript font editor and converter.</p>
  </background>
  <description>
    <p>FontForge is vulnerable to an error when processing the
      "CHARSET_REGISTRY" header in font files, which could cause a stack-based
      buffer overflow.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could entice a user to open a specially crafted BDF
      file using FontForge font editor, possibly resulting in the remote
      execution of arbitrary code with the privileges of the FontForge process,
      or a Denial of Service (application crash).
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All FontForge users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=media-gfx/fontforge-20110222-r1"
    </code>
    
    <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
      available since October 12, 2011. It is likely that your system is
      already no longer affected by this issue.
    </p>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4259">CVE-2010-4259</uri>
  </references>
  <metadata timestamp="2011-10-12T15:24:32Z" tag="requester">
    underling
  </metadata>
  <metadata timestamp="2012-01-23T11:57:55Z" tag="submitter">ackle</metadata>
</glsa>