NATS Server: Incomplete Stripping of Nats-Request-Info Header Allows Identity Spoofing
- 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. 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nats-io nats-server
fixed in 2.11.15; From 2.12.0-RC.1 · fixed in 2.12.6
- github.com/nats-io/nats-serverGo
All versions
- github.com/nats-io/nats-server/v2Go
fixed in 2.11.15; From 2.12.0-RC.1 · fixed in 2.12.6
- github.com/nats-io/nats-server/v2Go
fixed in 2.11.15
- github.com/nats-io/nats-server/v2Go
From 2.12.0-RC.1 · fixed in 2.12.6