Memory disclosure via incorrect JIT property read
Published May 16, 2022 · Updated Mar 6, 2025
Out-of-bounds read in PCRE2 before 10.40 allows context-dependent attackers to disclose process memory or crash a host application. The compile_xclass_matchingpath() path in pcre2_jit_compile.c reads the wrong property-type byte while compiling caseless Unicode property expressions. An embedding application must accept attacker-controlled expressions and enable JIT; consequences are bounded to memory disclosure or service interruption.
Summary
What happened
Out-of-bounds read in PCRE2 before 10.40 allows context-dependent attackers to disclose process memory or crash a host application. The compile_xclass_matchingpath() path in pcre2_jit_compile.c reads the wrong property-type byte while compiling caseless Unicode property expressions. An embedding application must accept attacker-controlled expressions and enable JIT; consequences are bounded to memory disclosure or service interruption.
The record
- CVE
- CVE-2022-1586
- Published
- May 16, 2022
- Updated
- Mar 6, 2025
- Vendor
- PCRE2 Project
- Product
- PCRE2
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2022CVE publishedPublication date reported by the CVE source.
- Mar 6, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in pcre2-10.40.
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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