Unauthenticated process crash via oversized polling POST
Published Jan 7, 2021 · Updated Aug 4, 2024
Resource exhaustion in Engine.IO before 3.6.0 allows remote attackers to crash the Node.js process through an oversized long-polling POST request. The transport accepts bodies up to the 100 MB default maxHttpBufferSize, allowing packet parsing to consume CPU and exhaust the V8 heap. No authentication or user interaction is required, and a sufficiently large payload terminates the server process.
Summary
What happened
Resource exhaustion in Engine.IO before 3.6.0 allows remote attackers to crash the Node.js process through an oversized long-polling POST request. The transport accepts bodies up to the 100 MB default maxHttpBufferSize, allowing packet parsing to consume CPU and exhaust the V8 heap. No authentication or user interaction is required, and a sufficiently large payload terminates the server process.
The record
- CVE
- CVE-2020-36048
- Published
- Jan 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- kill-engine-iofunctional · demonstrated
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