NATS: Message tracing can be redirected to arbitrary subject
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. Starting in version 2.11.0 and prior to versions 2.11.15 and 2.12.6, a valid client which uses message tracing headers can indicate that the trace messages can be sent to an arbitrary valid subject, including those to which the client does not have publish permission. The payload is a valid trace message and not chosen by the attacker. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.
From the CVE record · GitHub_M
A valid NATS-Server client using message tracing headers can direct trace messages to any valid subject, even one it cannot publish to. The payload is a valid trace message, not one chosen by the client. This requires a valid client; no user interaction is described.
Check deployments using Go github.com/nats-io/nats-server/v2 versions >=2.11.0 <2.11.15 or >=2.12.0-preview.1 <2.12.6, and users of the github.com/nats-io/nats-server package, for which no fixed version is listed.