Trusted-sender impersonation via Olm/Megolm protocol confusion
Published Sep 28, 2022 · Updated Apr 23, 2025
Protocol confusion in matrix-js-sdk before 19.7.0 allows remote attackers to impersonate trusted senders through crafted to-device messages. The to-device decryption path accepts Megolm-encrypted messages where Olm is required and derives their origin from homeserver-controlled fields instead of the authenticating Olm session. Exploitation requires an attacker cooperating with a malicious homeserver and enables forged messages or malicious key-backup injection.
Summary
What happened
Protocol confusion in matrix-js-sdk before 19.7.0 allows remote attackers to impersonate trusted senders through crafted to-device messages. The to-device decryption path accepts Megolm-encrypted messages where Olm is required and derives their origin from homeserver-controlled fields instead of the authenticating Olm session. Exploitation requires an attacker cooperating with a malicious homeserver and enables forged messages or malicious key-backup injection.
The record
- CVE
- CVE-2022-39251
- Published
- Sep 28, 2022
- Updated
- Apr 23, 2025
- Vendor
- The Matrix.org Foundation
- Product
- matrix-js-sdk
- Classifications
- CWE-287, CWE-322, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 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=< 19.7.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