Callout value corruption via overflowing numeric argument
Published Jun 15, 2020 · Updated Aug 4, 2024
Integer overflow in PCRE before 8.44 allows attackers to make applications receive an incorrect callout number via a crafted pattern. The compile_branch routine accumulates decimal digits after (?C in a signed integer before enforcing the 0–255 range, so an overlarge value wraps and can pass validation. Reachability requires an application to compile attacker-controlled regular expressions and use a callout callback; the library returns a corrupted callout number, with no demonstrated memory corruption.
Summary
What happened
Integer overflow in PCRE before 8.44 allows attackers to make applications receive an incorrect callout number via a crafted pattern. The compile_branch routine accumulates decimal digits after (?C in a signed integer before enforcing the 0–255 range, so an overlarge value wraps and can pass validation. Reachability requires an application to compile attacker-controlled regular expressions and use a callout callback; the library returns a corrupted callout number, with no demonstrated memory corruption.
The record
- CVE
- CVE-2020-14155
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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