Service hang via unescaped CPE regular expression
Published Dec 23, 2021 · Updated Aug 4, 2024
Regular expression injection in cve-search before 4.1.0 allows remote attackers to hang the service through crafted CPE input. The cvesForCPE function in lib/DatabaseLayer.py inserted cpe_regex directly into re.compile instead of escaping it. An unauthenticated network request reaching that function with a pathological pattern can consume excessive CPU during regular-expression evaluation.
Summary
What happened
Regular expression injection in cve-search before 4.1.0 allows remote attackers to hang the service through crafted CPE input. The cvesForCPE function in lib/DatabaseLayer.py inserted cpe_regex directly into re.compile instead of escaping it. An unauthenticated network request reaching that function with a pathological pattern can consume excessive CPU during regular-expression evaluation.
The record
- CVE
- CVE-2021-45470
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1333, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE 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