NATS has pre-auth server panic via leafnode handling
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 |
| No fix yet |
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. Prior to versions 2.11.15 and 2.12.6, a client which can connect to the leafnode port can crash the nats-server with a certain malformed message pre-authentication. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, disable leafnode support if not needed or restrict network connections to the leafnode port, if plausible without compromising the service offered.
From the CVE record · GitHub_M
NATS-Server can crash when it receives a malformed message on its leafnode port. A client with network access to that port can trigger the crash before authentication; no user interaction is required.
Operators using Go package github.com/nats-io/nats-server/v2 before 2.11.15 or from 2.12.0-RC.1 to before 2.12.6, or github.com/nats-io/nats-server at any version, should check their deployments.