blob: 126e9fa57233b187857703ea0e249377a4eae953 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200407-18">
<title>mod_ssl: Format string vulnerability</title>
<synopsis>
A bug in mod_ssl may allow a remote attacker to execute arbitrary code when
Apache is configured to use mod_ssl and mod_proxy.
</synopsis>
<product type="ebuild">mod_ssl</product>
<announced>2004-07-22</announced>
<revised count="01">2004-07-22</revised>
<bug>57379</bug>
<access>remote</access>
<affected>
<package name="net-www/mod_ssl" auto="yes" arch="*">
<unaffected range="ge">2.8.19</unaffected>
<vulnerable range="le">2.8.18</vulnerable>
</package>
</affected>
<background>
<p>
mod_ssl provides Secure Sockets Layer encryption and authentication to
Apache 1.3.
</p>
</background>
<description>
<p>
A bug in ssl_engine_ext.c makes mod_ssl vulnerable to a ssl_log() related
format string vulnerability in the mod_proxy hook functions.
</p>
</description>
<impact type="normal">
<p>
Given the right server configuration, an attacker could execute code as the
user running Apache, usually "apache".
</p>
</impact>
<workaround>
<p>
A server should not be vulnerable if it is not using both mod_ssl and
mod_proxy. Otherwise there is no workaround other than to disable mod_ssl.
</p>
</workaround>
<resolution>
<p>
All mod_ssl users should upgrade to the latest version:
</p>
<code>
# emerge sync
# emerge -pv ">=net-www/mod_ssl-2.8.19"
# emerge ">=net-www/mod_ssl-2.8.19"</code>
</resolution>
<references>
<uri link="http://marc.theaimsgroup.com/?l=apache-modssl&m=109001100906749&w=2">mod_ssl Announcement</uri>
</references>
<metadata tag="submitter">
jaervosz
</metadata>
</glsa>
|
GitWeb
