CVE-2011-1153: High severity php vulnerability

Published Mar 16, 2011
·
Updated

Multiple format string vulnerabilities in pharobject.c in the phar extension in PHP 5.3.5 and earlier allow context-dependent attackers to obtain sensitive information from process memory, cause a denial of service (memory corruption), or possibly execute arbitrary code via format string specifiers in an argument to a class method, leading to an incorrect zendthrowexceptionex call.

Other sources

Several format string flaws were found in PHP's Phar extension [1] that could be used to leak some parts of memory via error messages. These have been corrected in upstream svn [2]. The Phar extension is part of PHP since 5.3.0.

This is demonstrated with the following:

<?php

$x = new PharData('a.php'); $x->loadPhar("%08x.%08x.%08x.%08x.%08x");

?>

% php phar.php PHP Fatal error: Uncaught exception 'PharException' with message 'unable to open phar for reading "00000000.00000008.00000000.bffb3624.081ef712"' in /tmp/tests/phar.php:4 Stack trace: #0 /tmp/tests/phar.php(4): PharData::loadPhar('%08x.%08x.%08x....') #1 {main} thrown in /tmp/tests/phar.php on line 4

[1] http://bugs.php.net/bug.php?id=54247 [2] http://svn.php.net/viewvc?view=revision&revision=309221

Red Hat

Affected Software

104 affected components
PHP PHP=4.3.9
PHP PHP=4.4.9
PHP PHP=3.0
PHP PHP=5.2.9
PHP PHP=4.0-beta1
PHP PHP=3.0.5
PHP PHP=3.0.11
PHP PHP=5.1.5
PHP PHP=5.1.2
PHP PHP=4.0-beta4
PHP PHP=5.3.1
PHP PHP=4.2.0
PHP PHP=5.1.1
PHP PHP=3.0.1
PHP PHP=5.2.14
PHP PHP=3.0.2
PHP PHP=4.4.4
PHP PHP=5.0.0-beta1
PHP PHP=4.1.0
PHP PHP=5.1.6
PHP PHP=4.3.4
PHP PHP=4.0.4
PHP PHP=4.3.0
PHP PHP=4.0.5
PHP PHP=5.2.2
PHP PHP=3.0.8
PHP PHP=5.0.5
PHP PHP=4.3.6
PHP PHP=3.0.13
PHP PHP=5.0.1
PHP PHP=5.1.4
PHP PHP=5.2.5
PHP PHP=4.3.7
PHP PHP=5.0.4
PHP PHP=4.2.2
PHP PHP=4.4.2
PHP PHP=5.2.12
PHP PHP=3.0.7
PHP PHP=4.3.2
PHP PHP=4.3.11
PHP PHP=4.0.0
PHP PHP=3.0.6
PHP PHP=3.0.17
PHP PHP=4.0.7
PHP PHP=4.0.2
PHP PHP=4.3.3
PHP PHP=2.0
PHP PHP=4.1.1
PHP PHP=3.0.15
PHP PHP=3.0.16
PHP PHP=5.2.11
PHP PHP=5.2.6
PHP PHP=5.3.0
PHP PHP=4.4.3
PHP PHP=5.0.0-rc2
PHP PHP=5.2.3
PHP PHP=5.3.3
PHP PHP=5.0.3
PHP PHP=3.0.10
PHP PHP=3.0.4
PHP PHP=4.2.3
PHP PHP=5.1.0
PHP PHP=4.4.5
PHP PHP=5.2.13
PHP PHP=5.0.0-rc3
PHP PHP=4.0-beta2
PHP PHP=2.0b10
PHP PHP=4.4.8
PHP PHP=4.0.6
PHP PHP=5.2.0
PHP PHP=5.2.4
PHP PHP=4.1.2
PHP PHP=5.0.0-beta3
PHP PHP=5.3.2
PHP PHP<=5.3.5
PHP PHP=5.3.4
PHP PHP=4.3.1
PHP PHP=5.1.3
PHP PHP=3.0.18
PHP PHP=4.0-beta_4_patch1
PHP PHP=4.4.0
PHP PHP=5.2.10
PHP PHP=4.3.10
PHP PHP=4.2.1
PHP PHP=5.0.0-rc1
PHP PHP=4.0.1
PHP PHP=1.0
PHP PHP=5.0.2
PHP PHP=4.4.6
PHP PHP=3.0.12
PHP PHP=4.4.1
PHP PHP=4.0-beta3
PHP PHP=5.2.1
PHP PHP=4.0.3
PHP PHP=3.0.14
PHP PHP=3.0.9
PHP PHP=3.0.3
PHP PHP=5.0.0-beta4
PHP PHP=5.0.0
PHP PHP=4.3.8
PHP PHP=4.3.5
PHP PHP=5.0.0-beta2
PHP PHP=5.2.8
PHP PHP=4.4.7

Event History

Mar 16, 2011
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Data Sourced
10:02 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2011-1153?

CVE-2011-1153 is classified as a high severity vulnerability due to the potential for sensitive information disclosure and arbitrary code execution.

2

How do I fix CVE-2011-1153?

To fix CVE-2011-1153, upgrade to PHP version 5.3.6 or later as it addresses the format string vulnerabilities.

3

What types of vulnerabilities are present in CVE-2011-1153?

CVE-2011-1153 includes multiple format string vulnerabilities that can lead to memory corruption and potential arbitrary code execution.

4

Which PHP versions are affected by CVE-2011-1153?

CVE-2011-1153 affects PHP 5.3.5 and earlier versions, as well as several older versions down to 1.0.

5

What impact can an attack exploiting CVE-2011-1153 have on my system?

Exploiting CVE-2011-1153 can result in denial of service, memory corruption, and potentially full system compromise.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203