Client hang via cyclic room predecessor traversal
Published Aug 20, 2024 · Updated Sep 3, 2024
Uncontrolled recursion in matrix-js-sdk before 34.3.1 allows remote attackers to hang clients through cyclic room predecessor chains. The findPredecessorRooms traversal follows predecessor identifiers without tracking visited rooms, so getRoomUpgradeHistory never terminates when a cycle returns to a seen room. An attacker-controlled homeserver must supply the cyclic structure, and the client must inspect upgrade history or leave the room; the bounded consequence is a client hang.
Summary
What happened
Uncontrolled recursion in matrix-js-sdk before 34.3.1 allows remote attackers to hang clients through cyclic room predecessor chains. The findPredecessorRooms traversal follows predecessor identifiers without tracking visited rooms, so getRoomUpgradeHistory never terminates when a cycle returns to a seen room. An attacker-controlled homeserver must supply the cyclic structure, and the client must inspect upgrade history or leave the room; the bounded consequence is a client hang.
The record
- CVE
- CVE-2024-42369
- Published
- Aug 20, 2024
- Updated
- Sep 3, 2024
- Vendor
- The Matrix.org Foundation
- Product
- matrix-js-sdk
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Sep 3, 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=< 34.3.1
What conditions does exploitation require?
What is affected?
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