NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers
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. The nats-server offers a `Nats-Request-Info:` message header, providing information about a request. This is supposed to provide enough information to allow for account/user identification, such that NATS clients could make their own decisions on how to trust a message, provided that they trust the nats-server as a broker. A leafnode connecting to a nats-server is not fully trusted unless the system account is bridged too. Thus identity claims should not have propagated unchecked. Prior to versions 2.11.15 and 2.12.6, NATS clients relying upon the Nats-Request-Info: header could be spoofed. This does not directly affect the nats-server itself, but the CVSS Confidentiality and Integrity scores are based upon what a hypothetical client might choose to do with this NATS 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 could propagate unchecked identity claims in the Nats-Request-Info header from a leafnode that is not fully trusted. A client that relies on this header to identify an account or user could be deceived; the impact depends on what that client does with the information. This does not directly affect NATS-Server itself.
Engineers running github.com/nats-io/nats-server/v2 before 2.11.15 or from 2.12.0-RC.1 through versions before 2.12.6, or any version of github.com/nats-io/nats-server, should check their deployments.