Process crash via malformed recursive back reference
Published Jan 14, 2020 · Updated Aug 6, 2024
Out-of-bounds read in PCRE before 8.37 allows context-dependent attackers to crash a consuming process via a crafted regular expression. A group combining a forward subroutine call with a recursive back reference causes pcre_compile2 to emit incorrect compiled code and read one byte beyond its buffer. A consuming application must accept attacker-influenced patterns and compile them; the bounded consequence is a process-level denial of service.
Summary
What happened
Out-of-bounds read in PCRE before 8.37 allows context-dependent attackers to crash a consuming process via a crafted regular expression. A group combining a forward subroutine call with a recursive back reference causes pcre_compile2 to emit incorrect compiled code and read one byte beyond its buffer. A consuming application must accept attacker-influenced patterns and compile them; the bounded consequence is a process-level denial of service.
The record
- CVE
- CVE-2015-2326
- Published
- Jan 14, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Exim Bugzilla issue 1592 test caseproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo