NATS: Message tracing can be redirected to arbitrary subject
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.11.15, 2.12.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nats-io nats-server
From 2.11.0 · fixed in 2.11.15; From 2.12.0-preview.1 · fixed in 2.12.6
- github.com/nats-io/nats-server/v2Go
From 2.11.0 · fixed in 2.11.15
- github.com/nats-io/nats-server/v2Go
From 2.12.0-preview.1 · fixed in 2.12.6
- github.com/nats-io/nats-serverGo
All versions
- github.com/nats-io/nats-server/v2Go
From 2.11.0 · fixed in 2.11.15; From 2.12.0-preview.1 · fixed in 2.12.6