CVE-2012-1171: Infoleak

Published Mar 13, 2012

Updated

From PHP bug 61367:

The libxml RSHUTDOWN function disables the hooks which are used to implement openbasedir. It is possible to run user code after RSHUTDOWN, for example using the streamclose() 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.

Other sources

The libxml RSHUTDOWN function in PHP 5.x allows remote attackers to bypass the openbasedir protection mechanism and read arbitrary files via vectors involving a streamclose method call during use of a custom stream wrapper.

— MITRE

Affected Software

112 affected components

PHP PHP=5.0.0

PHP PHP=5.0.0-beta1

PHP PHP=5.0.0-beta2

PHP PHP=5.0.0-beta3

PHP PHP=5.0.0-beta4

PHP PHP=5.0.0-rc1

PHP PHP=5.0.0-rc2

PHP PHP=5.0.0-rc3

PHP PHP=5.0.1

PHP PHP=5.0.2

PHP PHP=5.0.3

PHP PHP=5.0.4

PHP PHP=5.0.5

PHP PHP=5.1.0

PHP PHP=5.1.1

PHP PHP=5.1.2

PHP PHP=5.1.3

PHP PHP=5.1.4

PHP PHP=5.1.5

PHP PHP=5.1.6

PHP PHP=5.2.0

PHP PHP=5.2.1

PHP PHP=5.2.2

PHP PHP=5.2.3

PHP PHP=5.2.4

PHP PHP=5.2.5

PHP PHP=5.2.6

PHP PHP=5.2.7

PHP PHP=5.2.8

PHP PHP=5.2.9

PHP PHP=5.2.10

PHP PHP=5.2.11

PHP PHP=5.2.12

PHP PHP=5.2.13

PHP PHP=5.2.14

PHP PHP=5.2.15

PHP PHP=5.2.16

PHP PHP=5.2.17

PHP PHP=5.3.0

PHP PHP=5.3.1

PHP PHP=5.3.2

PHP PHP=5.3.3

PHP PHP=5.3.4

PHP PHP=5.3.5

PHP PHP=5.3.6

PHP PHP=5.3.7

PHP PHP=5.3.8

PHP PHP=5.3.9

PHP PHP=5.3.10

PHP PHP=5.3.11

PHP PHP=5.3.12

PHP PHP=5.3.13

PHP PHP=5.3.14

PHP PHP=5.3.15

PHP PHP=5.3.16

PHP PHP=5.3.17

PHP PHP=5.3.18

PHP PHP=5.3.19

PHP PHP=5.3.20

PHP PHP=5.3.21

PHP PHP=5.3.22

PHP PHP=5.3.23

PHP PHP=5.3.24

PHP PHP=5.3.25

PHP PHP=5.3.26

PHP PHP=5.3.27

PHP PHP=5.4.0

PHP PHP=5.4.1

PHP PHP=5.4.2

PHP PHP=5.4.3

PHP PHP=5.4.4

PHP PHP=5.4.5

PHP PHP=5.4.6

PHP PHP=5.4.7

PHP PHP=5.4.8

PHP PHP=5.4.9

PHP PHP=5.4.10

PHP PHP=5.4.11

PHP PHP=5.4.12

PHP PHP=5.4.12-rc1

PHP PHP=5.4.12-rc2

PHP PHP=5.4.13

PHP PHP=5.4.13-rc1

PHP PHP=5.4.14

PHP PHP=5.4.14-rc1

PHP PHP=5.4.15-rc1

PHP PHP=5.4.16-rc1

PHP PHP=5.4.17

PHP PHP=5.4.18

PHP PHP=5.4.19

PHP PHP=5.4.20

PHP PHP=5.4.21

PHP PHP=5.4.22

PHP PHP=5.4.23

PHP PHP=5.5.0-alpha1

PHP PHP=5.5.0-alpha2

PHP PHP=5.5.0-alpha3

PHP PHP=5.5.0-alpha4

PHP PHP=5.5.0-alpha5

PHP PHP=5.5.0-alpha6

PHP PHP=5.5.0-beta1

PHP PHP=5.5.0-beta2

PHP PHP=5.5.0-beta3

PHP PHP=5.5.0-beta4

PHP PHP=5.5.0-rc1

PHP PHP=5.5.0-rc2

PHP PHP=5.5.1

PHP PHP=5.5.2

PHP PHP=5.5.3

PHP PHP=5.5.4

PHP PHP=5.5.5

PHP PHP=5.5.6

Event History

Mar 13, 2012

Data Sourced

02:35 AM

DescriptionSeverityAffected Software

Feb 15, 2014

CVE Published

via MITRE·11:00 AM

Data Sourced

via MITRE·11:00 AM

Description

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.