summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-201006-14.xml
blob: 7647e0789e399e6d84d2049266741fb020423202 (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
59
60
61
62
63
64
65
66
67
68
69
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201006-14">
  <title>Newt: User-assisted execution of arbitrary code</title>
  <synopsis>
    A heap-based buffer overflow in the Newt library might allow remote,
    user-assisted attackers to execute arbitrary code.
  </synopsis>
  <product type="ebuild">newt</product>
  <announced>2010-06-02</announced>
  <revised count="01">2010-06-02</revised>
  <bug>285854</bug>
  <access>remote</access>
  <affected>
    <package name="dev-libs/newt" auto="yes" arch="*">
      <unaffected range="ge">0.52.10-r1</unaffected>
      <vulnerable range="lt">0.52.10-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    Newt is a library for displaying text mode user interfaces.
    </p>
  </background>
  <description>
    <p>
    Miroslav Lichvar reported that Newt is prone to a heap-based buffer
    overflow in textbox.c.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could entice a user to enter a specially crafted
    string into a text dialog box rendered by Newt, possibly resulting in
    the remote execution of arbitrary code with the privileges of the user
    running the application, or a Denial of Service condition.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All Newt users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=dev-libs/newt-0.52.10-r1"</code>
    <p>
    NOTE: This is a legacy GLSA. Updates for all affected architectures are
    available since October 26, 2009. It is likely that your system is
    already no longer affected by this issue.
    </p>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2905">CVE-2009-2905</uri>
  </references>
  <metadata tag="requester" timestamp="2009-11-06T09:28:48Z">
    keytoaster
  </metadata>
  <metadata tag="submitter" timestamp="2010-05-31T05:47:34Z">
    a3li
  </metadata>
  <metadata tag="bugReady" timestamp="2010-05-31T05:47:41Z">
    a3li
  </metadata>
</glsa>