metadata/glsa/glsa-200803-19.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

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200803-19">
  <title>Apache: Multiple vulnerabilities</title>
  <synopsis>
    Multiple vulnerabilities have been discovered in Apache.
  </synopsis>
  <product type="ebuild">apache</product>
  <announced>2008-03-11</announced>
  <revised count="02">2008-03-12</revised>
  <bug>201163</bug>
  <bug>204410</bug>
  <bug>205195</bug>
  <bug>209899</bug>
  <access>remote</access>
  <affected>
    <package name="www-servers/apache" auto="yes" arch="*">
      <unaffected range="ge">2.2.8</unaffected>
      <vulnerable range="lt">2.2.8</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    The Apache HTTP server is one of the most popular web servers on the
    Internet.
    </p>
  </background>
  <description>
    <p>
    Adrian Pastor and Amir Azam (ProCheckUp) reported that the HTTP Method
    specifier header is not properly sanitized when the HTTP return code is
    "413 Request Entity too large" (CVE-2007-6203). The mod_proxy_balancer
    module does not properly check the balancer name before using it
    (CVE-2007-6422). The mod_proxy_ftp does not define a charset in its
    answers (CVE-2008-0005). Stefano Di Paola (Minded Security) reported
    that filenames are not properly sanitized within the mod_negotiation
    module (CVE-2008-0455, CVE-2008-0456).
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could entice a user to visit a malicious URL or send
    specially crafted HTTP requests (i.e using Adobe Flash) to perform
    Cross-Site Scripting and HTTP response splitting attacks, or conduct a
    Denial of Service attack on the vulnerable web server.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All Apache users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=www-servers/apache-2.2.8"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6203">CVE-2007-6203</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6422">CVE-2007-6422</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0005">CVE-2008-0005</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0455">CVE-2008-0455</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0456">CVE-2008-0456</uri>
  </references>
  <metadata tag="requester" timestamp="2008-01-13T14:04:58Z">
    jaervosz
  </metadata>
  <metadata tag="submitter" timestamp="2008-03-10T12:30:36Z">
    p-y
  </metadata>
  <metadata tag="bugReady" timestamp="2008-03-10T12:31:50Z">
    p-y
  </metadata>
</glsa>