Vulnerability Report: GO-2023-2133
- CVE-2023-47090, GHSA-fr2g-9hjm-wr23
- Affects: github.com/nats-io/nats-server/v2
- Published: Oct 24, 2023
- Modified: Nov 27, 2023
Without any authorization rules in the nats-server, users can connect without authentication. Before nats-server 2.2.0, all authentication and authorization rules for a nats-server lived in an "authorization" block, defining users. With nats-server 2.2.0 all users live inside accounts. When using the authorization block, whose syntax predates this, those users will be placed into the implicit global account, "$G". Users inside accounts go into the newer "accounts" block. If an "accounts" block is defined, in simple deployment scenarios this is often used only to enable client access to the system account. When the only account added is the system account "$SYS", the nats-server would create an implicit user in "$G" and set it as the `no_auth_user` account, enabling the same "without authentication" logic as without any rules. This preserved the ability to connect simply, and then add one authenticated login for system access. But with an "authorization" block, this is wrong. Users exist in the global account, with login rules. And in simple testing, they might still connect fine without administrators seeing that authentication has been disabled. In the fixed versions, using an "authorization" block will inhibit the implicit creation of a "$G" user and setting it as the `no_auth_user` target. In unfixed versions, just creating a second account, with no users, will also inhibit this behavior.
For detailed information about this vulnerability, visit https://advisories.nats.io/CVE/secnote-2023-01.txt.
from v2.2.0 before v2.9.23, from v2.10.0 before v2.10.2
- Alex Herrington