Security readout for executives and security teams
Plain-English summary
Rocket.Chat versions before 4.6.4 could write OAuth tokens into plaintext logs. If those logs were accessible, copied, backed up, or ingested into monitoring tools, sensitive tokens may have been exposed. The issue is confidentiality-focused and rated medium, not a service-disruption flaw.
Executive priority
Prioritize remediation for internet-facing or business-critical Rocket.Chat deployments, especially where logs are broadly accessible or centrally retained. Treat confirmed token exposure as a credential-handling incident.
Technical view
CVE-2022-32217 is CWE-312 cleartext storage of sensitive information in Rocket.Chat before 4.6.4. The CVE states OAuth tokens were leaked in plaintext Rocket.Chat logs. The supplied CVSS 3.1 score is 5.3, with confidentiality impact only.
Likely exposure
Exposure is most likely for organizations running Rocket.Chat below 4.6.4 where application logs were retained, exported, backed up, or readable by more than tightly trusted administrators.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Risk depends on whether exposed logs contained valid OAuth tokens and who could access those logs.
Researcher notes
The provided evidence identifies the product, version boundary, weakness class, and leaked data type, but does not include exploit details, active exploitation evidence, or complete vendor remediation guidance beyond the fixed version.
Mitigation direction
- Upgrade Rocket.Chat to 4.6.4 or later.
- Check Rocket.Chat guidance for any token revocation or cleanup steps.
- Restrict access to Rocket.Chat application logs and log exports.
- Review SIEM, backup, and support bundles for retained sensitive logs.
Validation and detection
- Inventory Rocket.Chat deployments and confirm all are 4.6.4 or later.
- Identify log stores receiving Rocket.Chat application logs.
- Review retained logs for plaintext OAuth token exposure.
- Confirm upgraded instances no longer write OAuth tokens into logs.
- Assess whether exposed logs were accessible outside trusted administrators.
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-312: 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-32217 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
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1394399CVE 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 Storage of Sensitive Information
Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.