CyberRota Analysis
AI-GeneratedThe matrix-sdk-crypto library, used for end-to-end encryption in Matrix clients, is vulnerable due to a lack of user ID verification when decrypting Olm-encrypted events, specifically those containing the `sender_device_keys` property. This flaw could allow an attacker, in collusion with the homeserver operator, to forge encrypted to-device events, potentially compromising the integrity of encrypted communications. Developers and security teams utilizing versions 0.12.0 to 0.16.0 of the matrix-sdk-crypto crate should prioritize upgrading to version 0.17.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
matrix-sdk-crypto is a no-network-IO implementation of a state machine that handles end-to-end encryption for Matrix clients. Starting in version 0.12.0 and prior to version 0.17.0, the matrix-sdk-crypto crate was missing a check for the user ID when decrypting an Olm-encrypted event containing the `sender_device_keys` property. This could be exploited to forge an encrypted to-device event, but only if the attacker colludes with the homeserver operator. This issue is fixed in matrix-sdk-crypto 0.17.0. There are no known workarounds for the issue.