PHP up to 5.6.30/7.0.20/7.1.6 Date Extension parse_date.c php_parse_date information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in PHP up to 5.6.30/7.0.20/7.1.6. Affected is the function php_parse_date of the file ext/date/lib/parse_date.c of the component Date Extension. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2017-11145. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in PHP up to 5.6.30/7.0.20/7.1.6 (Programming Language Software). This affects the function php_parse_date of the file ext/date/lib/parse_date.c of the component Date Extension. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

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 timelib_meridian parsing code could be used by attackers able to supply date strings to leak information from the interpreter, related to an ext/date/lib/parse_date.c out-of-bounds read affecting the php_parse_date function.

The bug was discovered 07/05/2017. The weakness was disclosed 07/10/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2017-11145 since 07/10/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 101908 (Debian DLA-1034-1 : php5 security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196874 (Ubuntu Security Notification for Php5, Php7.0 Vulnerabilities (USN-3382-1)).

Upgrading to version 5.6.31, 7.0.21 or 7.1.7 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (101908) and SecurityFocus (BID 99550†). The entries VDB-97454, VDB-103373, VDB-103374 and VDB-103375 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 101908
Nessus Name: Debian DLA-1034-1 : php5 security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 103043
OpenVAS Name: PHP Multiple Vulnerabilities - Jul17 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: PHP 5.6.31/7.0.21/7.1.7
Patch: e8b7698f5ee757ce2c8bd10a192a491a498f891c

Timelineinfo

07/05/2017 🔍
07/10/2017 +5 days 🔍
07/10/2017 +0 days 🔍
07/10/2017 +0 days 🔍
07/10/2017 +0 days 🔍
07/11/2017 +1 days 🔍
07/21/2017 +10 days 🔍
07/24/2017 +3 days 🔍
12/12/2022 +1967 days 🔍

Sourcesinfo

Product: php.org

Advisory: RHSA-2018:1296
Researcher: l dot wei
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-11145 (🔍)
GCVE (CVE): GCVE-0-2017-11145
GCVE (VulDB): GCVE-100-103377

OVAL: 🔍

SecurityFocus: 99550 - PHP CVE-2017-11145 Out of Bounds Read Information Disclosure Vulnerability

See also: 🔍

Entryinfo

Created: 07/11/2017 12:45
Updated: 12/12/2022 09:33
Changes: 07/11/2017 12:45 (80), 10/24/2019 16:18 (5), 12/31/2020 13:12 (2), 12/12/2022 09:33 (5)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!