Service interruption via unbounded user-agent regex evaluation
Published Mar 22, 2021 · Updated Sep 16, 2024
ReDoS in JefferyHus es6-crawler-detect before 3.1.3 allows remote attackers to interrupt service via crafted user-agent strings. The user-agent scanning path passes an unrestricted string to regular-expression matchers, allowing excessive CPU consumption during evaluation. Exploitation requires a consuming application to process attacker-controlled request headers; the documented consequence is degraded availability without data disclosure or modification.
Summary
What happened
ReDoS in JefferyHus es6-crawler-detect before 3.1.3 allows remote attackers to interrupt service via crafted user-agent strings. The user-agent scanning path passes an unrestricted string to regular-expression matchers, allowing excessive CPU consumption during evaluation. Exploitation requires a consuming application to process attacker-controlled request headers; the documented consequence is degraded availability without data disclosure or modification.
The record
- CVE
- CVE-2020-28501
- Published
- Mar 22, 2021
- Updated
- Sep 16, 2024
- Vendor
- JefferyHus
- Product
- es6-crawler-detect
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.1.3
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