| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/nats-io/nats-server | all versions | |
| github.com/nats-io/nats-server/v2 | ≥ 2.12.0-RC.1, < 2.12.6< 2.11.15 | 2.12.62.11.15 |
| nats-server | ≥ 2.12.0, < 2.12.6< 2.11.15 | 2.12.62.11.15 |
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.
The nats-server allows hub/spoke topologies using "leafnode" connections by other nats-servers. NATS messages can have headers.
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.
Thus NATS clients relying upon the Nats-Request-Info: header could be spoofed.
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.
Any version before v2.12.6 or v2.11.15
None.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free