Moleculer: Unauthenticated Denial of Service via negative length field in the TCP transporter packet parser
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in moleculer 0.14.36 and moleculer 0.15.2.
Moleculer is a progressive microservices framework for Node.js. Prior to 0.14.36 and 0.15.2, Parser._write in src/transporters/tcp/parser.js used Buffer.prototype.readInt32BE to read a signed packet length, so a remote unauthenticated peer could supply a negative value that caused packet.slice(length) to return the unchanged buffer while the while (packet.length > 0) loop continued indefinitely. The synchronous loop blocked the Node.js event loop and made every service in the process unresponsive until restart. The TCP transporter must be enabled and reachable, and neither CRC validation nor maxPacketSize prevents the malformed length value. This issue is fixed in versions 0.14.36 and 0.15.2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| moleculerjs | <0.14.36, >=0.15.0 <0.15.2 | ||
| npm: moleculer | <0.14.36, >=0.15.0-beta1 <0.15.2 | 0.14.36, 0.15.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket