Quick answers
- Is CVE-2016-10160 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-10160 being exploited in the wild.
- How severe is CVE-2016-10160?
- Critical severity, with a CVSS score of 9.8, published 24 January 2017.
- Which products and versions are affected?
- PHP Group PHP before 5.6.30, 7.0.x before 7.0.15.
- Is there a fix for CVE-2016-10160?
- A patch was published on 2017-01-19: PHP 5.6.30 release date Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-10160 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2016-10160?
- Check whether you run Debian Linux, NetApp Clustered Data Ontap or PHP Group PHP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An off-by-one error exists in the 'phar_parse_pharfile' function within 'ext/phar/phar.c' in PHP. The vulnerability is triggered when processing a crafted PHAR archive that contains an alias mismatch. This memory corruption flaw can be exploited by a remote, unauthenticated attacker to cause a denial of service (crash) or potentially achieve remote code execution (RCE). The issue was addressed in PHP versions 5.6.30 and 7.0.15.
Affected products
- PHP PHP before 5.6.30, 7.0.x before 7.0.15
Timeline
- 2017-01-24: advisory: NVD publication date
- 2017-01-19: patched: PHP 5.6.30 release date