NATS JetStream has an authorization bypass through its Management API
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. Prior to versions 2.11.15 and 2.12.6, users with JetStream admin API access to restore one stream could restore to other stream names, impacting data which should have been protected against them. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, if developers have configured users to have limited JetStream restore permissions, temporarily remove those permissions.
From the CVE record · GitHub_M
NATS-Server allows users with JetStream admin API access to restore one stream to other stream names. This can affect data that should be protected from those users. The attacker needs JetStream admin API access to restore a stream.
Check deployments using Go package github.com/nats-io/nats-server/v2 before 2.11.15 or from 2.12.0-RC.1 through versions before 2.12.6, and deployments using github.com/nats-io/nats-server, for which all versions are affected.