redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length above 2^32-1 to crash the Node.js client process.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
noderedis:redis-parser
References 7
https://github.com/NodeRedis/node-redis-parser/issues/65
GitHub Issue #65
https://github.com/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e4…
NVD
https://github.com/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e4…
NVD
https://github.com/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e4…
NVD
https://github.com/NodeRedis/node-redis-parser/issues/47
NVD
https://github.com/NodeRedis/node-redis-parser
NVD
https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-servi…
VulnCheck Advisory: redis-parser through 3.0.0 Denial of Service via Invalid Array Length