Remote service interruption via hash-colliding route cache
Published Jun 2, 2021 · Updated Aug 4, 2024
Uncontrolled resource consumption in Red Hat RESTEasy 4.5.5.Final and earlier allows remote attackers to make HTTP endpoints unresponsive. RootNode inserts colliding route keys into an unbounded cache, making each lookup and insertion consume progressively more CPU. No authentication or user interaction is required; repeated requests can stall the affected application without affecting confidentiality or integrity.
Summary
What happened
Uncontrolled resource consumption in Red Hat RESTEasy 4.5.5.Final and earlier allows remote attackers to make HTTP endpoints unresponsive. RootNode inserts colliding route keys into an unbounded cache, making each lookup and insertion consume progressively more CPU. No authentication or user interaction is required; repeated requests can stall the affected application without affecting confidentiality or integrity.
The record
- CVE
- CVE-2020-14326
- Published
- Jun 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- RESTEasy
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=RESTEasy 4.5.6.Final
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