blob: 5a6d84a313acbaab785c59df8932ec592d253e82 (
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
72
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200402-01">
<title>PHP setting leaks from .htaccess files on virtual hosts</title>
<synopsis>
If the server configuration "php.ini" file has
"register_globals = on" and a request is made to one virtual host
(which has "php_admin_flag register_globals off") and the next
request is sent to the another virtual host (which does not have the
setting) global variables may leak and may be used to exploit the
site.
</synopsis>
<product type="ebuild">PHP</product>
<announced>2004-02-07</announced>
<revised count="01">2004-02-07</revised>
<bug>39952</bug>
<access>remote</access>
<affected>
<package name="dev-php/mod_php" auto="yes" arch="*">
<unaffected range="ge">4.3.4-r4</unaffected>
<vulnerable range="lt">4.3.4-r4</vulnerable>
</package>
</affected>
<background>
<p>
PHP is a widely-used general-purpose scripting language that is
especially suited for Web development and can be embedded into HTML.
</p>
</background>
<description>
<p>
If the server configuration "php.ini" file has
"register_globals = on" and a request is made to one virtual host
(which has "php_admin_flag register_globals off") and the next
request is sent to the another virtual host (which does not have the
setting) through the same apache child, the setting will persist.
</p>
</description>
<impact type="normal">
<p>
Depending on the server and site, an attacker may be able to exploit
global variables to gain access to reserved areas, such as MySQL passwords,
or this vulnerability may simply cause a lack of functionality. As a
result, users are urged to upgrade their PHP installations.
</p>
<p>
Gentoo ships PHP with "register_globals" set to "off"
by default.
</p>
<p>
This issue affects both servers running Apache 1.x and servers running
Apache 2.x.
</p>
</impact>
<workaround>
<p>
No immediate workaround is available; a software upgrade is required.
</p>
</workaround>
<resolution>
<p>
All users are recommended to upgrade their PHP installation to 4.3.4-r4:
</p>
<code>
# emerge sync
# emerge -pv ">=dev-php/mod_php-4.3.4-r4"
# emerge ">=dev-php/mod_php-4.3.4-r4"</code>
</resolution>
<references>
<uri link="https://bugs.php.net/bug.php?id=25753">Corresponding PHP bug</uri>
</references>
</glsa>
|