glsa-200411-31.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

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200411-31">
  <title>ProZilla: Multiple vulnerabilities</title>
  <synopsis>
    ProZilla contains several buffer overflow vulnerabilities that can be
    exploited by a malicious server to execute arbitrary code with the rights
    of the user running ProZilla.
  </synopsis>
  <product type="ebuild">ProZilla</product>
  <announced>2004-11-23</announced>
  <revised count="03">2006-05-22</revised>
  <bug>70090</bug>
  <access>remote</access>
  <affected>
    <package name="www-client/prozilla" auto="yes" arch="*">
      <vulnerable range="le">1.3.7.3</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    ProZilla is a download accelerator for Linux.
    </p>
  </background>
  <description>
    <p>
    ProZilla contains several exploitable buffer overflows in the code
    handling the network protocols.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could setup a malicious server and entice a user to
    retrieve files from that server using ProZilla. This could lead to the
    execution of arbitrary code with the rights of the user running
    ProZilla.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    Currently, there is no released version of ProZilla that contains a fix
    for these issues. The original author did not respond to our queries,
    the code contains several other problems and more secure alternatives
    exist. Therefore, the ProZilla package has been hard-masked prior to
    complete removal from Portage, and current users are advised to unmerge
    the package.
    </p>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1120">CVE-2004-1120</uri>
  </references>
  <metadata tag="requester" timestamp="2004-11-22T17:28:48Z">
    koon
  </metadata>
  <metadata tag="bugReady" timestamp="2004-11-22T19:27:08Z">
    koon
  </metadata>
  <metadata tag="submitter" timestamp="2004-11-22T19:46:53Z">
    koon
  </metadata>
</glsa>