CWE
200
Advisory Published
CVE Published
Updated

CVE-2010-2531: Infoleak

First published: Fri Jul 09 2010(Updated: )

The upstream PHP 5.2.14 and 5.3.3 releases corrected an information disclosure flaw where the var_export() function would disclose data if a fatal error occurred due to recursion, memory_limit, or execution time. The buffer is never cleared and is flushed to the user, regardless of the configured display_errors setting, because it is considered part of the output. This could lead to a disclosure of possibly sensitive information. The name <a href="https://access.redhat.com/security/cve/CVE-2010-2531">CVE-2010-2531</a> has been assigned to this issue. An example to test: % cat test.php #!/usr/bin/php &lt;?php @$obj-&gt;p =&amp; $obj; var_export($obj, true); ?&gt; % php test.php PHP Fatal error: Nesting level too deep - recursive dependency? in test.php on line 4 stdClass::__set_state(array( 'p' =&gt; stdClass::__set_state(array( 'p' =&gt; stdClass::__set_state(array( 'p' =&gt; stdClass::__set_state(array( % cat test2.php #!/usr/bin/php &lt;?php $a[] =&amp; $a; var_export($a, true); ?&gt; % php test2.php PHP Fatal error: Nesting level too deep - recursive dependency? in test.php on line 4 array ( 0 =&gt; array ( 0 =&gt; array ( 0 =&gt; array ( 0 =&gt; array ( The upstream changes prevent any output from displaying, so should only display the "PHP Fatal error". The upstream fix: <a href="http://svn.php.net/viewvc?view=revision&amp;revision=301143">http://svn.php.net/viewvc?view=revision&amp;revision=301143</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/php<0:5.1.6-27.el5_5.3
0:5.1.6-27.el5_5.3
PHP>=5.2.0<5.2.14
PHP>=5.3.0<5.3.3
Debian Linux=5.0
Debian Linux=6.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2010-2531?

    CVE-2010-2531 has been classified as a moderate security vulnerability.

  • How do I fix CVE-2010-2531?

    To fix CVE-2010-2531, upgrade to PHP versions 5.2.14 or 5.3.3 or later.

  • What types of systems are affected by CVE-2010-2531?

    CVE-2010-2531 affects systems running PHP versions up to 5.2.14 and 5.3.3, particularly on Red Hat and Debian distributions.

  • What does CVE-2010-2531 mean for my PHP applications?

    CVE-2010-2531 could lead to sensitive data exposure in PHP applications during fatal errors due to recursive calls or resource limits.

  • Is CVE-2010-2531 a zero-day vulnerability?

    No, CVE-2010-2531 is not a zero-day vulnerability as it was publicly disclosed and patched in 2010.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203