summaryrefslogtreecommitdiff
blob: 091991335e07ef601275bbc5467823a5fe304ac4 (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
70
71
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200504-11">
  <title>JunkBuster: Multiple vulnerabilities</title>
  <synopsis>
    JunkBuster is vulnerable to a heap corruption vulnerability, and under
    certain configurations may allow an attacker to modify settings.
  </synopsis>
  <product type="ebuild">junkbuster</product>
  <announced>2005-04-13</announced>
  <revised count="02">2005-04-21</revised>
  <bug>88537</bug>
  <access>remote</access>
  <affected>
    <package name="net-proxy/junkbuster" auto="yes" arch="*">
      <unaffected range="ge">2.0.2-r3</unaffected>
      <vulnerable range="lt">2.0.2-r3</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    JunkBuster is a filtering HTTP proxy, designed to enhance privacy and
    remove unwanted content.
    </p>
  </background>
  <description>
    <p>
    James Ranson reported a vulnerability when JunkBuster is configured to
    run in single-threaded mode, an attacker can modify the referrer
    setting by getting a victim to request a specially crafted URL
    (CAN-2005-1108). Tavis Ormandy of the Gentoo Linux Security Audit Team
    identified a heap corruption issue in the filtering of URLs
    (CAN-2005-1109).
    </p>
  </description>
  <impact type="high">
    <p>
    If JunkBuster has been configured to run in single-threaded mode, an
    attacker can disable or modify the filtering of Referrer: HTTP headers,
    potentially compromising the privacy of users. The heap corruption
    vulnerability could crash or disrupt the operation of the proxy,
    potentially executing arbitrary code.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All JunkBuster users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-proxy/junkbuster-2.0.2-r3"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-1108">CAN-2005-1108</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-1109">CAN-2005-1109</uri>
  </references>
  <metadata tag="requester" timestamp="2005-04-12T20:24:12Z">
    jaervosz
  </metadata>
  <metadata tag="submitter" timestamp="2005-04-12T21:28:36Z">
    taviso
  </metadata>
  <metadata tag="bugReady" timestamp="2005-04-13T08:43:25Z">
    koon
  </metadata>
</glsa>