CVE-2012-2376: Buffer Overflow

Published May 21, 2012
·
Updated

A security flaw was found in the way the comprinttypeinfo() routine of the PHP scripting language processed certain COM object arguments. If a PHP language based application remotely accepted untrusted comprinttypeinfo() arguments in order to print out a PHP class definition for a dispatchable interface, a remote attacker could provide a specially-crafted COM object, which once processed by the application could lead to that application crash, or, potentially arbitrary code execution with the privileges of the user running the application.

References: [1] https://isc.sans.edu/diary/PHP+5+4+Remote+Exploit+PoC+in+the+wild/13255 [2] http://packetstormsecurity.org/files/112851/php54-exec.txt [3] http://www.exploit-db.com/exploits/18861/ [4] http://www.reddit.com/r/netsec/comments/tuyp3/iscdiaryphp54remoteexploitpocinthewild/

CVE request: [5] http://www.openwall.com/lists/oss-security/2012/05/20/1

CVE assignment: [6] http://www.openwall.com/lists/oss-security/2012/05/20/2

Other sources

Buffer overflow in the comprinttypeinfo function in PHP 5.4.3 and earlier on Windows allows remote attackers to execute arbitrary code via crafted arguments that trigger incorrect handling of COM object VARIANT types, as exploited in the wild in May 2012.

MITRE

Affected Software

117 affected components
PHP PHP<=5.4.3
PHP PHP=1.0
PHP PHP=2.0
PHP PHP=2.0b10
PHP PHP=3.0
PHP PHP=3.0.1
PHP PHP=3.0.2
PHP PHP=3.0.3
PHP PHP=3.0.4
PHP PHP=3.0.5
PHP PHP=3.0.6
PHP PHP=3.0.7
PHP PHP=3.0.8
PHP PHP=3.0.9
PHP PHP=3.0.10
PHP PHP=3.0.11
PHP PHP=3.0.12
PHP PHP=3.0.13
PHP PHP=3.0.14
PHP PHP=3.0.15
PHP PHP=3.0.16
PHP PHP=3.0.17
PHP PHP=3.0.18
PHP PHP=4.0-beta_4_patch1
PHP PHP=4.0-beta1
PHP PHP=4.0-beta2
PHP PHP=4.0-beta3
PHP PHP=4.0-beta4
PHP PHP=4.0.0
PHP PHP=4.0.1
PHP PHP=4.0.2
PHP PHP=4.0.3
PHP PHP=4.0.4
PHP PHP=4.0.5
PHP PHP=4.0.6
PHP PHP=4.0.7
PHP PHP=4.1.0
PHP PHP=4.1.1
PHP PHP=4.1.2
PHP PHP=4.2.0
PHP PHP=4.2.1
PHP PHP=4.2.2
PHP PHP=4.2.3
PHP PHP=4.3.0
PHP PHP=4.3.1
PHP PHP=4.3.2
PHP PHP=4.3.3
PHP PHP=4.3.4
PHP PHP=4.3.5
PHP PHP=4.3.6
PHP PHP=4.3.7
PHP PHP=4.3.8
PHP PHP=4.3.9
PHP PHP=4.3.10
PHP PHP=4.3.11
PHP PHP=4.4.0
PHP PHP=4.4.1
PHP PHP=4.4.2
PHP PHP=4.4.3
PHP PHP=4.4.4
PHP PHP=4.4.5
PHP PHP=4.4.6
PHP PHP=4.4.7
PHP PHP=4.4.8
PHP PHP=4.4.9
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.4.0
PHP PHP=5.4.1
PHP PHP=5.4.2
Microsoft Windows

Event History

May 21, 2012
Data Sourced
10:20 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2376?

CVE-2012-2376 is classified as a medium severity vulnerability that can lead to remote code execution.

2

How do I fix CVE-2012-2376?

To fix CVE-2012-2376, upgrade PHP to version 5.4.4 or later, or apply relevant patches.

3

What versions of PHP are affected by CVE-2012-2376?

CVE-2012-2376 affects PHP versions up to and including 5.4.3.

4

Can CVE-2012-2376 be exploited remotely?

Yes, CVE-2012-2376 can be exploited remotely if a vulnerable application accepts untrusted arguments.

5

What is the impact of CVE-2012-2376?

The impact of CVE-2012-2376 includes the potential for attackers to execute arbitrary code on the affected server.

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