glsa-200511-10.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
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200511-10">
  <title>RAR: Format string and buffer overflow vulnerabilities</title>
  <synopsis>
    RAR contains a format string error and a buffer overflow vulnerability that
    may be used to execute arbitrary code.
  </synopsis>
  <product type="ebuild">rar</product>
  <announced>2005-11-13</announced>
  <revised count="01">2005-11-13</revised>
  <bug>111926</bug>
  <access>remote</access>
  <affected>
    <package name="app-arch/rar" auto="yes" arch="*">
      <unaffected range="ge">3.5.1</unaffected>
      <vulnerable range="lt">3.5.1</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    RAR is a powerful archive manager that can decompress RAR, ZIP and
    other files, and can create new archives in RAR and ZIP file format.
    </p>
  </background>
  <description>
    <p>
    Tan Chew Keong reported about two vulnerabilities found in RAR:
    </p>
    <ul>
    <li>A format string error exists when displaying a diagnostic
    error message that informs the user of an invalid filename in an
    UUE/XXE encoded file.</li>
    <li>Some boundary errors in the processing
    of malicious ACE archives can be exploited to cause a buffer
    overflow.</li>
    </ul>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could exploit these vulnerabilities by enticing
    a user to:
    </p>
    <ul><li>decode a specially crafted UUE/XXE file,
    or</li>
    <li>extract a malicious ACE archive containing a file with an
    overly long filename.</li>
    </ul>
    <p>
    When the user performs these
    actions, the arbitrary code of the attacker's choice will be executed.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All RAR users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=app-arch/rar-3.5.1"</code>
  </resolution>
  <references>
    <uri link="http://www.rarlabs.com/rarnew.htm">RAR Release Notes</uri>
    <uri link="https://secunia.com/secunia_research/2005-53/advisory/">Secunia Research 11/10/2005</uri>
  </references>
  <metadata tag="requester" timestamp="2005-11-11T09:12:31Z">
    jaervosz
  </metadata>
  <metadata tag="submitter" timestamp="2005-11-11T14:35:09Z">
    adir
  </metadata>
  <metadata tag="bugReady" timestamp="2005-11-11T14:35:22Z">
    adir
  </metadata>
</glsa>