Security readout for executives and security teams
Plain-English summary
Some older NATS messaging servers may let an authenticated user receive messages they were explicitly denied. This weakens access controls inside message-driven systems and could expose or alter limited data flows, depending on how NATS subjects are used.
Executive priority
Treat as a moderate-priority access-control fix. Prioritize quickly if NATS carries sensitive business events, customer data, operational commands, or supports multiple teams or tenants with different access rights.
Technical view
NATS Server before 2.8.2 and Streaming Server before 0.24.6 failed to enforce negative user permissions in one scenario. The CVE describes queue subscriptions involving wildcards allowing denied subjects. CVSS 3.1 is 6.3: network reachable, low complexity, low privileges required, no user interaction.
Likely exposure
Exposure is most likely where affected NATS versions are deployed with authenticated users, deny permissions, and subject-based separation between tenants, services, or data classes. The bundle does not provide CPEs or deployment-specific affected package metadata.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Exploitation requires a remote user with valid low-privileged access, so risk is higher in shared, partner-accessible, or multi-tenant messaging environments.
Researcher notes
The public bundle identifies the vulnerable behavior and fixed version thresholds but omits CWE, CPEs, detailed affected package metadata, and exploitation evidence. Validation should focus on version confirmation and whether deny permissions are security-critical in the deployment.
Mitigation direction
- Upgrade NATS Server to 2.8.2 or later.
- Upgrade NATS Streaming Server to 0.24.6 or later.
- Review NATS advisory and vendor guidance for configuration-specific notes.
- Restrict NATS access to trusted networks and authenticated principals.
- Audit deny-based subject permissions in shared environments.
Validation and detection
- Inventory deployed NATS Server and Streaming Server versions.
- Confirm no instance runs below 2.8.2 or 0.24.6 respectively.
- Review account and user permission models for deny rules.
- Check whether NATS subjects separate sensitive services or tenants.
- Review logs for unexpected access to denied subject areas.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-29946 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nats-io/advisories/blob/main/CVE/CVE-2022-29946.txtCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
