Application crash via unchecked forward-reference repetition
Published Jan 14, 2020 · Updated Aug 6, 2024
Heap buffer overflow in PCRE before 8.37 allows context-dependent attackers to crash applications via a crafted regular expression. The compile_branch function insufficiently bounds repeated forward references while compiling a zero-minimum repeated outer group, causing an out-of-bounds heap read and incorrect compiled code. Reachability depends on an embedding application accepting attacker-controlled patterns; the documented consequence is a process crash, while other impact is unspecified.
Summary
What happened
Heap buffer overflow in PCRE before 8.37 allows context-dependent attackers to crash applications via a crafted regular expression. The compile_branch function insufficiently bounds repeated forward references while compiling a zero-minimum repeated outer group, causing an out-of-bounds heap read and incorrect compiled code. Reachability depends on an embedding application accepting attacker-controlled patterns; the documented consequence is a process crash, while other impact is unspecified.
The record
- CVE
- CVE-2015-2325
- Published
- Jan 14, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-125
- 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream crafted-pattern reproducerproof 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