Security readout for executives and security teams
Plain-English summary
Rocket.Chat versions before v5 allowed any logged-in user to view direct messages they should not be able to access. This is a confidentiality issue, not a system takeover. Business urgency depends on whether Rocket.Chat contains sensitive internal, customer, legal, or incident-response conversations.
Executive priority
Handle as a moderate-priority confidentiality risk. Prioritize faster remediation where Rocket.Chat is internet-facing, widely accessible, or used for sensitive business discussions. The issue does not indicate unauthenticated compromise or data modification in the provided sources.
Technical view
CVE-2022-35250 is a CWE-732 privilege/permission issue in Rocket.Chat <v5. With network access and a valid account, an attacker could access direct messages without proper authorization. CVSS 3.1 is 4.3: low complexity, authenticated, no user interaction, confidentiality impact only.
Likely exposure
Exposure is likely limited to organizations running Rocket.Chat versions before v5 and allowing user authentication. The issue requires a valid account, so risk rises in large workspaces, externally reachable deployments, or environments with many low-trust users.
Exploitation context
The provided sources do not indicate CISA KEV listing or active exploitation. Public disclosure exists through the CVE record and HackerOne reference, but the bundle does not provide evidence of real-world exploitation.
Researcher notes
The bundle identifies the vulnerability class, affected range, CVSS vector, and HackerOne reference, but does not include detailed exploit mechanics or complete remediation guidance. Avoid assuming affected forks, cloud services, or active exploitation without additional vendor evidence.
Mitigation direction
- Inventory all Rocket.Chat deployments and identify versions below v5.
- Upgrade affected Rocket.Chat instances to a vendor-fixed v5 or later release.
- Review Rocket.Chat vendor guidance for any version-specific remediation notes.
- Restrict or remove unnecessary user accounts until affected systems are remediated.
- Treat sensitive direct-message content as potentially exposed on vulnerable deployments.
Validation and detection
- Confirm production and staging Rocket.Chat versions are not below v5.
- Verify authentication is required and anonymous access is not unexpectedly enabled.
- Review user roles and permissions for unusual direct-message access patterns.
- Check logs for unexpected access to direct-message resources, where available.
- Document remediation status for each Rocket.Chat instance.
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-732: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-35250 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/917946CVE 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.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.