What is the severity of CVE-2016-9138?

CVE-2016-9138 has a moderate severity level due to its potential for causing denial of service.

How do I fix CVE-2016-9138?

To fix CVE-2016-9138, upgrade PHP to version 5.6.28 or newer, or to any version in the 7.1 series or later.

What versions of PHP are affected by CVE-2016-9138?

CVE-2016-9138 affects PHP versions up to 5.6.27 and from 7.0.0 up to 7.0.12.

Can CVE-2016-9138 lead to remote code execution?

CVE-2016-9138 does not directly lead to remote code execution but may be exploited for denial of service and other unspecified impacts.

What is the attack vector for CVE-2016-9138?

CVE-2016-9138 can be exploited by remote attackers through crafted serialized data during the __wakeup processing.

Vulnerability/
CVE-2016-9138

critical

9.8

CWE

416

4/1/2017

6/8/2024

CVE-2016-9138: Use After Free

First published: Wed Jan 04 2017(Updated: )

PHP through 5.6.27 and 7.x through 7.0.12 mishandles property modification during __wakeup processing, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted serialized data, as demonstrated by Exception::__toString with DateInterval::__wakeup.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
PHP	<=5.6.27
PHP	=7.0.0
PHP	=7.0.1
PHP	=7.0.2
PHP	=7.0.3
PHP	=7.0.4
PHP	=7.0.5
PHP	=7.0.6
PHP	=7.0.7
PHP	=7.0.8
PHP	=7.0.9
PHP	=7.0.10
PHP	=7.0.11
PHP	=7.0.12

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9138?
CVE-2016-9138 has a moderate severity level due to its potential for causing denial of service.
How do I fix CVE-2016-9138?
To fix CVE-2016-9138, upgrade PHP to version 5.6.28 or newer, or to any version in the 7.1 series or later.
What versions of PHP are affected by CVE-2016-9138?
CVE-2016-9138 affects PHP versions up to 5.6.27 and from 7.0.0 up to 7.0.12.
Can CVE-2016-9138 lead to remote code execution?
CVE-2016-9138 does not directly lead to remote code execution but may be exploited for denial of service and other unspecified impacts.
What is the attack vector for CVE-2016-9138?
CVE-2016-9138 can be exploited by remote attackers through crafted serialized data during the __wakeup processing.

agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/references
agent/weakness
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/php
canonical/php
version/php/5.6.27
version/php/7.0.0
version/php/7.0.1
version/php/7.0.2
version/php/7.0.3
version/php/7.0.4
version/php/7.0.5
version/php/7.0.6
version/php/7.0.7
version/php/7.0.8
version/php/7.0.9
version/php/7.0.10
version/php/7.0.11
version/php/7.0.12

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.

Frequently Asked Questions

What is the severity of CVE-2016-9138?
CVE-2016-9138 has a moderate severity level due to its potential for causing denial of service.
How do I fix CVE-2016-9138?
To fix CVE-2016-9138, upgrade PHP to version 5.6.28 or newer, or to any version in the 7.1 series or later.
What versions of PHP are affected by CVE-2016-9138?
CVE-2016-9138 affects PHP versions up to 5.6.27 and from 7.0.0 up to 7.0.12.
Can CVE-2016-9138 lead to remote code execution?
CVE-2016-9138 does not directly lead to remote code execution but may be exploited for denial of service and other unspecified impacts.
What is the attack vector for CVE-2016-9138?
CVE-2016-9138 can be exploited by remote attackers through crafted serialized data during the __wakeup processing.