NATS allows MQTT clients to bypass ACL checks
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, when using ACLs on message subjects, these ACLs were not applied in the `$MQTT.>` namespace, allowing MQTT clients to bypass ACL checks for MQTT subjects. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.
From the CVE record · GitHub_M
NATS-Server does not apply message-subject ACLs in the `$MQTT.>` namespace in affected versions. When subject ACLs are in use, MQTT clients can bypass ACL checks for MQTT subjects. The input does not specify whether authentication or user interaction is required.
Operators using `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 users of any version of `github.com/nats-io/nats-server`, should check their deployments.