Security readout for executives and security teams
Plain-English summary
Rocket.Chat could expose OAuth tokens to authenticated users who have the “view-full-other-user-info” permission. The issue affects Rocket.Chat versions before 4.7.5, 4.8.2, and 5.0.0. Token exposure can create account or integration compromise risk, but the provided sources do not show public exploitation.
Executive priority
Treat this as a moderate-priority confidentiality issue. It is not documented as actively exploited, but OAuth token leakage can affect trust boundaries between chat, identity, and integrations. Upgrade and permission review should be scheduled promptly.
Technical view
CVE-2022-32227 is a CWE-319 cleartext transmission issue in Rocket.Chat involving OAuth tokens returned or exposed through full other-user information access. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges, no user interaction, high confidentiality impact only.
Likely exposure
Exposure is likely limited to Rocket.Chat deployments running affected versions where users or roles have the “view-full-other-user-info” permission. Internet-facing instances increase business risk, but exploitation still requires authenticated access with the relevant permission.
Exploitation context
The source bundle lists KEV as false and provides no cited evidence of active exploitation. The vulnerability is confidentiality-focused: leaked OAuth tokens could enable unauthorized access depending on token scope and downstream integrations.
Researcher notes
Evidence is limited to the CVE record, CVE List data, and the referenced HackerOne report. The public summary does not provide detailed exploit mechanics, affected configurations beyond the permission, or vendor-specific post-exposure token guidance.
Mitigation direction
- Upgrade Rocket.Chat to 4.7.5, 4.8.2, 5.0.0, or later supported releases.
- Restrict “view-full-other-user-info” to trusted administrative roles until upgrade is complete.
- Review Rocket.Chat vendor guidance for any token handling or rotation recommendations.
- Prioritize externally reachable or heavily integrated Rocket.Chat deployments first.
Validation and detection
- Inventory Rocket.Chat versions across production, staging, and self-hosted instances.
- Confirm affected instances are upgraded to a fixed version or later.
- Review roles granted “view-full-other-user-info” and remove unnecessary assignments.
- Check authentication and audit logs for unusual user-information access patterns.
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-319: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-32227 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1517377CVE 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.
Cleartext Transmission of Sensitive Information
Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.