Security readout for executives and security teams
Plain-English summary
Some Zulip private streams could leak edited old messages to current stream subscribers who should not see pre-subscription history. Official Zulip clients ignored the event, but a modified client or browser developer tools could observe it. The issue is low severity because it is narrow, limited to confidentiality, and requires specific conditions.
Executive priority
Treat this as a targeted confidentiality bug, not a broad compromise indicator. Prioritize upgrade if Zulip private streams carry sensitive information or protected history is relied on for access control.
Technical view
Zulip Server 2.1.0 through 5.2 has a logic error affecting private streams with protected history. When an older message is edited, the server may send an API event containing that edited message to all current subscribers, including newer subscribers who should not receive past history. Fixed in Zulip Server 5.3; no workaround is listed.
Likely exposure
Exposure is limited to Zulip Server deployments running versions 2.1.0 through 5.2 that use private streams with protected history. The at-risk data is edited message content from before a subscriber joined that stream.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. Observability requires a modified client or browser developer tools because official clients ignore the event. The CVSS vector indicates network access, high privileges, high complexity, and user interaction.
Researcher notes
The affected behavior is server-side event emission, not display in official clients. Evidence in the bundle is sufficient for affected versions, trigger conditions, fixed version, and lack of workaround, but it does not provide exploitation telemetry or impact scope beyond edited message disclosure.
Mitigation direction
- Upgrade Zulip Server to version 5.3 or later.
- Review Zulip advisory guidance before relying on compensating controls.
- Do not assume a workaround; the advisory states none are known.
- Identify protected-history private streams that may contain sensitive history.
- Avoid sensitive edits in affected streams until the server is upgraded.
Validation and detection
- Inventory Zulip Server versions and flag 2.1.0 through 5.2.
- Confirm whether private streams use protected history.
- Review whether sensitive pre-subscription messages were edited while affected.
- Verify production is upgraded to Zulip Server 5.3 or later.
- Document any potentially exposed streams for incident review.
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-571: 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 lookupCWE-670: 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 lookupCVE-2022-31017 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
- Low
- CVSS
- 2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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:H/PR:H/UI:R/S:U/C:L/I:N/A:N0.51.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
2LowVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zulip/zulip/security/advisories/GHSA-m5j3-jp59-6f3qCVE reference · x_refsource_CONFIRM
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.
Expression is Always True
Expression is Always True represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Always-Incorrect Control Flow Implementation
Always-Incorrect Control Flow Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.