4_2_2.php

<?php
$_SERVER['BASE_PAGE'] = 'releases/4_2_2.php';
include_once __DIR__ . '/../include/prepend.inc';
site_header("PHP 4.2.2 Release Announcement");
?>

<h1>
 PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1
</h1>

<p>[ <a href="/releases/4_2_2_fr.php">Version Fran&ccedil;aise</a> ]</p>

<dl>
 <dt>Issued on:</dt>
 <dd>July 22, 2002</dd>
 <dt>Software:</dt>
 <dd>PHP versions 4.2.0 and 4.2.1</dd>
 <dt>Platforms:</dt>
 <dd>All</dd>
</dl>

<p>
 The PHP Group has learned of a serious security vulnerability in PHP
 versions 4.2.0 and 4.2.1. An intruder may be able to execute arbitrary
 code with the privileges of the web server. This vulnerability may be
 exploited to compromise the web server and, under certain conditions,
 to gain privileged access.
</p>

<h2>Description</h2>

<p>
 PHP contains code for intelligently parsing the headers of HTTP POST
 requests. The code is used to differentiate between variables and files
 sent by the user agent in a "multipart/form-data" request. This parser
 has insufficient input checking, leading to the vulnerability.
</p>

<p>
 The vulnerability is exploitable by anyone who can send HTTP POST
 requests to an affected web server. Both local and remote users, even
 from behind firewalls, may be able to gain privileged access.
</p>

<h2>Impact</h2>

<p>
 Both local and remote users may exploit this vulnerability to compromise
 the web server and, under certain conditions, to gain privileged access.
 So far only the IA32 platform has been verified to be safe from the
 execution of arbitrary code. The vulnerability can still be used on IA32
 to crash PHP and, in most cases, the web server.
</p>

<h2>Solution</h2>

<p>
 The PHP Group has released a new PHP version, 4.2.2, which incorporates
 a fix for the vulnerability. All users of affected PHP versions are
 encouraged to upgrade to this latest version. <a href="/downloads.php">The
 downloads page</a> has the new 4.2.2 source tarballs, Windows binaries
 and source patches from 4.2.0 and 4.2.1 available for download.
</p>

<h2>Workaround</h2>

<p>
 If the PHP applications on an affected web server do not rely on HTTP
 POST input from user agents, it is often possible to deny POST requests
 on the web server.
</p>

<p>
 In the Apache web server, for example, this is possible with the
 following code included in the main configuration file or a top-level
 .htaccess file:
</p>

<pre>
&lt;Limit POST&gt;
   Order deny,allow
   Deny from all
&lt;/Limit&gt;
</pre>

<p>
 Note that an existing configuration and/or .htaccess file may have
 parameters contradicting the example given above.
</p>

<h2>Credits</h2>

<p>
 The PHP Group would like to thank Stefan Esser of e-matters GmbH for
 discovering this vulnerability. e-matters GmbH has also released an
 <a href="http://security.e-matters.de/advisories/022002.html">independent
 advisory</a>, describing the vulnerability in more detail.
</p>

<?php site_footer(); ?>