CVE-2016-4072: Input Validation

Published May 20, 2016
·
Updated

Fixed bug (Invalid memory write in phar on filename with \0 in name). (CVE-2016-4072)

Other sources

The Phar extension in PHP before 5.5.34, 5.6.x before 5.6.20, and 7.x before 7.0.5 allows remote attackers to execute arbitrary code via a crafted filename, as demonstrated by mishandling of \0 characters by the pharanalyzepath function in ext/phar/phar.c.

Affected Software

82 affected componentsFixes available
debian/php5
debian/php7.0
PHP PHP=5.6.0-alpha1
PHP PHP=5.6.0-alpha2
PHP PHP=5.6.0-alpha3
PHP PHP=5.6.0-alpha4
PHP PHP=5.6.0-alpha5
PHP PHP=5.6.0-beta1
PHP PHP=5.6.0-beta2
PHP PHP=5.6.0-beta3
PHP PHP=5.6.0-beta4
PHP PHP=5.6.1
PHP PHP=5.6.2
PHP PHP=5.6.3
PHP PHP=5.6.4
PHP PHP=5.6.5
PHP PHP=5.6.6
PHP PHP=5.6.7
PHP PHP=5.6.8
PHP PHP=5.6.9
PHP PHP=5.6.10
PHP PHP=5.6.11
PHP PHP=5.6.12
PHP PHP=5.6.13
PHP PHP=5.6.14
PHP PHP=5.6.15
PHP PHP=5.6.16
PHP PHP=5.6.17
PHP PHP=5.6.18
PHP PHP=5.6.19
PHP PHP=7.0.0
PHP PHP=7.0.1
PHP PHP=7.0.2
PHP PHP=7.0.3
PHP PHP=7.0.4
Apple iOS and macOS<=10.11.4
PHP PHP=5.5.0
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
PHP PHP=5.5.7
PHP PHP=5.5.8
PHP PHP=5.5.9
PHP PHP=5.5.10
PHP PHP=5.5.11
PHP PHP=5.5.12
PHP PHP=5.5.13
PHP PHP=5.5.14
PHP PHP=5.5.15
PHP PHP=5.5.16
PHP PHP=5.5.17
PHP PHP=5.5.18
PHP PHP=5.5.19
PHP PHP=5.5.20
PHP PHP=5.5.21
PHP PHP=5.5.22
PHP PHP=5.5.23
PHP PHP=5.5.24
PHP PHP=5.5.25
PHP PHP=5.5.26
PHP PHP=5.5.27
PHP PHP=5.5.29
PHP PHP=5.5.30
PHP PHP=5.5.31
PHP PHP=5.5.32
PHP PHP=5.5.33
PHP PHP<7.0.5
7.0.5

Remediation

Patch Available

https://git.php.net/?p=php-src.git;a=commit;h=1e9b175204e3286d64dfd6c9f09151c31b5e099a

Event History

May 20, 2016
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:17 PM
Description
Sep 20, 2024
Data Sourced
via Ubuntu·01:14 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2016-4072?

CVE-2016-4072 has a high severity rating due to the potential for remote code execution via crafted filenames.

2

How do I fix CVE-2016-4072?

To mitigate CVE-2016-4072, upgrade PHP to versions 5.5.34, 5.6.20, or 7.0.5 or later.

3

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

CVE-2016-4072 affects PHP versions prior to 5.5.34, 5.6.x before 5.6.20, and 7.x before 7.0.5.

4

Can CVE-2016-4072 be exploited without authentication?

Yes, CVE-2016-4072 can be exploited by unauthenticated attackers through crafted input.

5

What type of vulnerability is CVE-2016-4072 classified as?

CVE-2016-4072 is classified as a remote code execution vulnerability.

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