PCRE up to 8.36 pcre_exec.c match Regex Pattern memory corruption

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.
9.4$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in PCRE up to 8.36. This affects the function Match of the file pcre_exec.c. Executing a manipulation with the input /(?:((abcd))|(((?:(?:(?:(?:abc|(?:abcdef))))b)abcdefghi)abc)|((*ACCEPT)))/ as part of Regex Pattern can lead to memory corruption. This vulnerability appears as CVE-2015-8382. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in PCRE up to 8.36 (Programming Tool Software). It has been declared as very critical. This vulnerability affects the function match of the file pcre_exec.c. The manipulation with the input value /(?:((abcd))|(((?:(?:(?:(?:abc|(?:abcdef))))b)abcdefghi)abc)|((*ACCEPT)))/ leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

The match function in pcre_exec.c in PCRE before 8.37 mishandles the /(?:((abcd))|(((?:(?:(?:(?:abc|(?:abcdef))))b)abcdefghi)abc)|((*ACCEPT)))/ pattern and related patterns involving (*ACCEPT), which allows remote attackers to obtain sensitive information from process memory or cause a denial of service (partially initialized memory and application crash) via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror, aka ZDI-CAN-2547.

The weakness was presented 12/02/2015 by Stanislav Malyshev (Website). The advisory is available at bugzilla.redhat.com. This vulnerability was named CVE-2015-8382 since 12/01/2015. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/28/2022).

The vulnerability scanner Nessus provides a plugin with the ID 95534 (SUSE SLED12 / SLES12 Security Update : pcre (SUSE-SU-2016:2971-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196440 (Ubuntu Security Notification for pcre3 vulnerabilities (USN-2943-1)).

Upgrading to version 8.37 eliminates this vulnerability. A possible mitigation has been published 2 years after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (95534) and SecurityFocus (BID 76157†). See VDB-75660, VDB-79370, VDB-79371 and VDB-79376 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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: 95534
Nessus Name: SUSE SLED12 / SLES12 Security Update : pcre (SUSE-SU-2016:2971-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 841810
OpenVAS Name: Ubuntu Update for pcre3 USN-2943-1
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
Exposure Time: 🔍

Upgrade: PCRE 8.37
Patch: c351b47ce85a3a147cfa801fa9f0149ab4160834

Timelineinfo

01/29/2015 🔍
12/01/2015 +306 days 🔍
12/01/2015 +0 days 🔍
12/02/2015 +1 days 🔍
12/03/2015 +1 days 🔍
12/02/2016 +365 days 🔍
12/05/2016 +3 days 🔍
06/28/2022 +2031 days 🔍

Sourcesinfo

Advisory: bugzilla.redhat.com
Researcher: Stanislav Malyshev
Status: Not defined
Confirmation: 🔍

CVE: CVE-2015-8382 (🔍)
GCVE (CVE): GCVE-0-2015-8382
GCVE (VulDB): GCVE-100-79378
SecurityFocus: 76157 - PHP PCRE Extension 'trunk/pcre_exec.c' Information Disclosure Vulnerability

See also: 🔍

Entryinfo

Created: 12/03/2015 09:43
Updated: 06/28/2022 10:04
Changes: 12/03/2015 09:43 (46), 04/22/2018 13:25 (29), 06/28/2022 10:04 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!