Service crash via attachment-count string concatenation
Published Jan 7, 2021 · Updated Aug 4, 2024
Resource exhaustion in socket.io-parser before 3.3.2 and version 3.4.0 allows remote attackers to crash Node.js services with a large packet. The decodeString function appends each character of an attacker-controlled attachment count into chained V8 ConsOneByteString objects before converting the resulting integer to a Number. An unauthenticated client that can reach the HTTP long-polling endpoint can exhaust the Node.js heap and terminate the hosting process with a single large POST request.
Summary
What happened
Resource exhaustion in socket.io-parser before 3.3.2 and version 3.4.0 allows remote attackers to crash Node.js services with a large packet. The decodeString function appends each character of an attacker-controlled attachment count into chained V8 ConsOneByteString objects before converting the resulting integer to a Number. An unauthenticated client that can reach the HTTP long-polling endpoint can exhaust the Node.js heap and terminate the hosting process with a single large POST request.
The record
- CVE
- CVE-2020-36049
- Published
- Jan 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, CWE-400, T1499
- 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