Room-state divergence via incomplete event authorization
Published Sep 2, 2022 · Updated Apr 23, 2025
Improper event authorization in Matrix.org Synapse 1.61.0 and earlier allows remote attackers to cause federated room-state divergence. The check_state_independent_auth_rules path accepts m.room.create events with previous events and duplicate or unexpected authorization events instead of rejecting them. Federation must be enabled, and a crafted event from another homeserver can leave participating servers with inconsistent room state and deny consistent room service.
Summary
What happened
Improper event authorization in Matrix.org Synapse 1.61.0 and earlier allows remote attackers to cause federated room-state divergence. The check_state_independent_auth_rules path accepts m.room.create events with previous events and duplicate or unexpected authorization events instead of rejecting them. Federation must be enabled, and a crafted event from another homeserver can leave participating servers with inconsistent room state and deny consistent room service.
The record
- CVE
- CVE-2022-31152
- Published
- Sep 2, 2022
- Updated
- Apr 23, 2025
- Vendor
- Matrix.org
- Product
- Synapse
- Classifications
- CWE-703, CWE-755, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 1.62.0
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