Security readout for executives and security teams
Plain-English summary
Authenticated Rocket.Chat users may have been able to see user lists for rooms they should not access. This is a confidentiality issue, not a takeover or service outage issue in the provided sources.
Executive priority
Treat as a medium-priority confidentiality fix. It can expose room membership information to authenticated users, so prioritize organizations using Rocket.Chat for sensitive internal or customer communications.
Technical view
The getUsersOfRoom Meteor server method did not type validate input. MongoDB query operator objects could be accepted instead of a room ID string, bypassing room access checks for matching rooms after the first match.
Likely exposure
Exposure is limited to Rocket.Chat deployments running affected versions before 4.7.5, 4.8.2, or 5.0.0. The CVSS vector requires low privileges, network access, and no user interaction.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Public HackerOne reporting is referenced, but the provided data does not establish exploitation in the wild.
Researcher notes
Evidence points to improper access control caused by missing type validation in a Meteor method. The provided sources name fixed versions but do not include exploit-in-the-wild evidence or detailed vendor mitigation beyond upgrading.
Mitigation direction
- Upgrade Rocket.Chat to 4.7.5, 4.8.2, 5.0.0, or a later supported release.
- Check Rocket.Chat guidance for any branch-specific remediation notes.
- Prioritize externally reachable or broadly accessible Rocket.Chat workspaces.
- Limit access to trusted authenticated users until upgraded, where operationally feasible.
Validation and detection
- Inventory all Rocket.Chat deployments and record exact server versions.
- Confirm no production instance is below the fixed version for its branch.
- Review access logs for unusual getUsersOfRoom activity, without attempting reproduction.
- Confirm post-upgrade tests cover room membership authorization boundaries.
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.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-32226 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1410357CVE reference · x_refsource_MISC
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.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.