CVE-2022-39252: matrix-sdk-crypto contains potential impersonation via room key forward responses
When matrix-rust-sdk before 0.6 requests a room key from our devices, it correctly accepts key forwards only if they are a response to a previous request. However, it doesn’t check that the device that responded matches the device the key was requested from.
This allows a malicious homeserver to insert room keys of questionable validity into the key store in some situations, potentially assisting in an impersonation attack. Note that even if key injection succeeds in this way, all forwarded keys have the imported
flag set, which is used as an indicator that such keys have lesser authentication properties (and should be marked as such in clients, e.g. with a grey shield besides the message).
References
- github.com/advisories/GHSA-vp68-2wrm-69qm
- github.com/matrix-org/matrix-rust-sdk
- github.com/matrix-org/matrix-rust-sdk/commit/093fb5d0aa21c0b5eaea6ec96b477f1075271cbb
- github.com/matrix-org/matrix-rust-sdk/commit/41449d2cc360e347f5d4e1c154ec1e3185f11acd
- github.com/matrix-org/matrix-rust-sdk/releases/tag/matrix-sdk-0.6.0
- github.com/matrix-org/matrix-rust-sdk/security/advisories/GHSA-vp68-2wrm-69qm
- nvd.nist.gov/vuln/detail/CVE-2022-39252
- rustsec.org/advisories/RUSTSEC-2022-0085.html
Detect and mitigate CVE-2022-39252 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →