CVE-2017-11145: Infoleak
Fixed bug (wddxdeserialize() heap out-of-bound read via phpparsedate()). (CVE-2017-11145)
Other sources
In PHP before 5.6.31, 7.x before 7.0.21, and 7.1.x before 7.1.7, an error in the date extension's timelibmeridian parsing code could be used by attackers able to supply date strings to leak information from the interpreter, related to ext/date/lib/parsedate.c out-of-bounds reads affecting the phpparsedate function. NOTE: the correct fix is in the e8b7698f5ee757ce2c8bd10a192a491a498f891c commit, not the bd77ac90d3bdf31ce2a5251ad92e9e75 gist.
In PHP before 5.6.31, 7.x before 7.0.21, and 7.1.x before 7.1.7, lack of a bounds check in the date extension's timelibmeridian parsing code could be used by attackers able to supply date strings to leak information from the interpreter, related to an ext/date/lib/parsedate.c out-of-bounds read affecting the phpparsedate function.
Upstream bug:
https://bugs.php.net/bug.php?id=74819
Upstream patch:
https://gist.github.com/anonymous/bd77ac90d3bdf31ce2a5251ad92e9e75
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID of this bug?
The vulnerability ID of this bug is CVE-2017-11145.
What is the severity of CVE-2017-11145?
The severity of CVE-2017-11145 is high with a CVSS score of 7.5.
What is the affected software?
The affected software includes PHP versions before 5.6.31, 7.0.21, and 7.1.7 as well as some specific versions from Red Hat, Ubuntu, and Debian repositories.
How can an attacker exploit CVE-2017-11145?
An attacker can exploit CVE-2017-11145 by supplying malicious date strings to the date extension's timelib_meridian parsing code, which can lead to information leakage and out-of-bounds reads.
Are there any remedies or fixes available for CVE-2017-11145?
Yes, the remediation steps vary depending on the affected software version, so it is recommended to update to the fixed versions provided by the respective vendors such as Red Hat, Ubuntu, and Debian.