nats-server websockets are vulnerable to pre-auth memory DoS
nats-io nats-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/nats-server/v2 Go |
|
|
| github.com/nats-io/nats-server Go |
|
nats-io nats-server
| Product | Affected | Fixed in |
|---|---|---|
| github.com/nats-io/nats-server/v2 Go |
|
|
| github.com/nats-io/nats-server Go |
|
| No fix yet |
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The WebSockets handling of NATS messages handles compressed messages via the WebSockets negotiated compression. Prior to versions 2.11.2 and 2.12.3, the implementation bound the memory size of a NATS message but did not independently bound the memory consumption of the memory stream when constructing a NATS message which might then fail validation for size reasons. An attacker can use a compression bomb to cause excessive memory consumption, often resulting in the operating system terminating the server process. The use of compression is negotiated before authentication, so this does not require valid NATS credentials to exploit. The fix, present in versions 2.11.2 and 2.12.3, was to bounds the decompression to fail once the message was too large, instead of continuing on. The vulnerability only affects deployments which use WebSockets and which expose the network port to untrusted end-points.
From the CVE record · GitHub_M
NATS-Server can consume excessive memory while decompressing a WebSockets message, potentially causing the operating system to terminate the server process. An attacker can trigger this without NATS credentials when a deployment uses WebSockets and exposes its network port to untrusted endpoints.
Check deployments using github.com/nats-io/nats-server/v2 before 2.11.12 or from 2.12.0-RC.1 through versions before 2.12.3, and deployments using github.com/nats-io/nats-server through 1.4.1.