CVE-2022-39252 json
When matrix-rust-sdk recieves forwarded room keys, the reciever doesn't check if it requested the key from the forwarder
published 4y ago modified 4mo ago also GHSA-vp68-2wrm-69qm , RUSTSEC-2022-0085 , EUVD-2022-6950
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust, and matrix-sdk-crypto is the Matrix encryption library. Prior to version 0.6, when a user requests a room key from their devices, the software correctly remembers the request. When the user receives a forwarded room key, the software accepts it without checking who the room key came from. This allows homeservers to try to insert room keys of questionable validity, potentially mounting an impersonation attack. Version 0.6 fixes this issue.
Patch / fix
- crates.io matrix-sdk-crypto 0.6.0
- matrix matrix-rust-sdk 0.6
Is CVE-2022-39252 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | matrix-sdk-crypto | <0.6.0 >=0.0.0-0, <0.6.0 |
0.6.0 |
Affected products
- matrix-org matrix-rust-sdk
Classification
References
-
github.com
/matrix-org/matrix-rust-sdk/commit/093fb5d0aa21c0b5eaea6ec96b477f1075271cbb
web, patch, third-party-advisory
-
github.com
/matrix-org/matrix-rust-sdk/commit/41449d2cc360e347f5d4e1c154ec1e3185f11acd
web, patch, third-party-advisory
-
github.com
/matrix-org/matrix-rust-sdk/security/advisories/GHSA-vp68-2wrm-69qm
web, third-party-advisory
-
github.com
/matrix-org/matrix-rust-sdk/releases/tag/matrix-sdk-0.6.0
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39252
advisory
-
github.com
/matrix-org/matrix-rust-sdk
package
-
rustsec.org
/advisories/RUSTSEC-2022-0085.html
web, advisory
-
crates.io
/crates/matrix-sdk-crypto
package
Sources
- CVE List CVE-2022-39252
- GitHub Advisory GHSA-vp68-2wrm-69qm
- NVD CVE-2022-39252
- OSV RUSTSEC-2022-0085
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.