NATS Server: Incomplete Stripping of Nats-Request-Info Header Allows Identity Spoofing
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, the NATS message header `Nats-Request-Info:` is supposed to be a guarantee of identity by the NATS server, but the stripping of this header from inbound messages was not fully effective. An attacker with valid credentials for any regular client interface could thus spoof their identity to services which rely upon this header. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.
From the CVE record · GitHub_M
NATS-Server does not fully strip the `Nats-Request-Info:` header from inbound messages. An attacker with valid credentials for a regular client interface can spoof their identity to services that rely on this header.
Check deployments using Go package github.com/nats-io/nats-server/v2 before 2.11.15 or from 2.12.0-RC.1 before 2.12.6, and deployments using the unversioned github.com/nats-io/nats-server package, for which all versions are affected.