medium
5
CWE
200
Advisory Published
CVE Published
Updated

CVE-2012-1171: Infoleak

First published: Tue Mar 13 2012(Updated: )

From PHP <a class="bz_bug_link bz_secure " title="" href="show_bug.cgi?id=61367">bug 61367</a>: The libxml RSHUTDOWN function disables the hooks which are used to implement open_basedir. It is possible to run user code after RSHUTDOWN, for example using the stream_close() method of a custom stream wrapper. Such code is able to read arbitrary files via libxml. The suggested fix is to move the code which disables the hooks to a post-deactivate function. All op arrays are destroyed before post-deactivate, so it is not possible for user code to be executed after post-deactivate.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
PHP=5.0.0
PHP=5.0.0-beta1
PHP=5.0.0-beta2
PHP=5.0.0-beta3
PHP=5.0.0-beta4
PHP=5.0.0-rc1
PHP=5.0.0-rc2
PHP=5.0.0-rc3
PHP=5.0.1
PHP=5.0.2
PHP=5.0.3
PHP=5.0.4
PHP=5.0.5
PHP=5.1.0
PHP=5.1.1
PHP=5.1.2
PHP=5.1.3
PHP=5.1.4
PHP=5.1.5
PHP=5.1.6
PHP=5.2.0
PHP=5.2.1
PHP=5.2.2
PHP=5.2.3
PHP=5.2.4
PHP=5.2.5
PHP=5.2.6
PHP=5.2.7
PHP=5.2.8
PHP=5.2.9
PHP=5.2.10
PHP=5.2.11
PHP=5.2.12
PHP=5.2.13
PHP=5.2.14
PHP=5.2.15
PHP=5.2.16
PHP=5.2.17
PHP=5.3.0
PHP=5.3.1
PHP=5.3.2
PHP=5.3.3
PHP=5.3.4
PHP=5.3.5
PHP=5.3.6
PHP=5.3.7
PHP=5.3.8
PHP=5.3.9
PHP=5.3.10
PHP=5.3.11
PHP=5.3.12
PHP=5.3.13
PHP=5.3.14
PHP=5.3.15
PHP=5.3.16
PHP=5.3.17
PHP=5.3.18
PHP=5.3.19
PHP=5.3.20
PHP=5.3.21
PHP=5.3.22
PHP=5.3.23
PHP=5.3.24
PHP=5.3.25
PHP=5.3.26
PHP=5.3.27
PHP=5.4.0
PHP=5.4.1
PHP=5.4.2
PHP=5.4.3
PHP=5.4.4
PHP=5.4.5
PHP=5.4.6
PHP=5.4.7
PHP=5.4.8
PHP=5.4.9
PHP=5.4.10
PHP=5.4.11
PHP=5.4.12
PHP=5.4.12-rc1
PHP=5.4.12-rc2
PHP=5.4.13
PHP=5.4.13-rc1
PHP=5.4.14
PHP=5.4.14-rc1
PHP=5.4.15-rc1
PHP=5.4.16-rc1
PHP=5.4.17
PHP=5.4.18
PHP=5.4.19
PHP=5.4.20
PHP=5.4.21
PHP=5.4.22
PHP=5.4.23
PHP=5.5.0-alpha1
PHP=5.5.0-alpha2
PHP=5.5.0-alpha3
PHP=5.5.0-alpha4
PHP=5.5.0-alpha5
PHP=5.5.0-alpha6
PHP=5.5.0-beta1
PHP=5.5.0-beta2
PHP=5.5.0-beta3
PHP=5.5.0-beta4
PHP=5.5.0-rc1
PHP=5.5.0-rc2
PHP=5.5.1
PHP=5.5.2
PHP=5.5.3
PHP=5.5.4
PHP=5.5.5
PHP=5.5.6

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2012-1171?

    CVE-2012-1171 is considered a high severity vulnerability due to its potential to bypass security restrictions.

  • How do I fix CVE-2012-1171?

    To fix CVE-2012-1171, upgrade your PHP version to a fixed version that addresses this vulnerability.

  • What versions of PHP are affected by CVE-2012-1171?

    CVE-2012-1171 affects PHP versions 5.0.0 to 5.5.6, including various beta and release candidates.

  • What is the impact of CVE-2012-1171?

    The impact of CVE-2012-1171 is that it can allow unauthorized access to files and run arbitrary user code.

  • Is CVE-2012-1171 publicly known?

    Yes, CVE-2012-1171 is a publicly documented vulnerability within the PHP bug tracking system.

Company

Resources

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