LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35249: A information disclosure vulnerability exists in Rocket.Chat <v5 where the getUserMentionsByChannel meteor...

A information disclosure vulnerability exists in Rocket.Chat <v5 where the getUserMentionsByChannel meteor server method discloses messages from private channels and direct messages regardless of the users access permission to the room.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Rocket.Chat versions before the fixed v5 release could expose messages from private channels and direct messages to an authenticated user through a mention-related server method. The issue is confidentiality-only, but it can still undermine trust in private communications if sensitive discussions occurred there.

Executive priority

Prioritize remediation for Rocket.Chat environments used for confidential internal, executive, legal, HR, or incident-response discussions. The issue is not a takeover bug, but private-message exposure can create business, privacy, and trust consequences.

Technical view

The vulnerable getUserMentionsByChannel Meteor server method failed to enforce room access permissions before returning message data. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, with low confidentiality impact and no integrity or availability impact.

Likely exposure

Organizations running Rocket.Chat before the fixed v5 release are the relevant exposure group, especially where many regular users have accounts. The source bundle does not identify hosted versus self-managed differences.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires an authenticated user account, is network-accessible, and targets disclosure of private channel or direct-message content rather than system takeover.

Researcher notes

Evidence is limited to the CVE metadata and HackerOne reference in the bundle. The affected range is described as Rocket.Chat before v5, with the bundle noting a fix in the v5 line. No exploit procedure, patch diff, or active exploitation source is provided.

Mitigation direction

  • Upgrade Rocket.Chat to the vendor-fixed v5 release or later.
  • Check Rocket.Chat vendor guidance before treating ambiguous versions as remediated.
  • Limit account access to trusted users until affected instances are upgraded.
  • Review sensitive private-room or direct-message content for potential disclosure impact.

Validation and detection

  • Inventory all Rocket.Chat deployments and record exact versions.
  • Flag any Rocket.Chat instance running before the fixed v5 release.
  • Confirm permission checks with authorized regression testing after upgrade.
  • Review available application logs for unusual mention-method activity, if logged.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
cve · low confidence lookup

CVE-2022-35249 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-35249Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aRocket.ChatFixed in version 5.0>Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.