Web-client interruption via repeated hidden-popover dismissal
Published Nov 29, 2024 · Updated Dec 2, 2024
Memory leak in Zulip 8.0 through 8.3 allows attackers to exhaust a web client's memory through repeated popover interactions. Multiple popover event handlers call Tippy's instance.hide() after the same popover has already been hidden instead of checking its visibility before a second dismissal. Triggering occurs through the web interface; published evidence supports browser-session interruption, not server shutdown, data access, or data modification.
Summary
What happened
Memory leak in Zulip 8.0 through 8.3 allows attackers to exhaust a web client's memory through repeated popover interactions. Multiple popover event handlers call Tippy's instance.hide() after the same popover has already been hidden instead of checking its visibility before a second dismissal. Triggering occurs through the web interface; published evidence supports browser-session interruption, not server shutdown, data access, or data modification.
The record
- CVE
- CVE-2024-36612
- Published
- Nov 29, 2024
- Updated
- Dec 2, 2024
- Vendor
- Zulip
- Product
- Zulip
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2024CVE publishedPublication date reported by the CVE source.
- Dec 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.0 <=8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo