Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| matrix-org | matrix-rust-sdk | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Matrix-org | Matrix-rust-sdk |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wfq4-36m3-9g42 | Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.308% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Matrix-org
Matrix-org matrix-rust-sdk |
|
| Vendors & Products |
Matrix-org
Matrix-org matrix-rust-sdk |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution | |
| Weaknesses | CWE-290 | |
| References |
| |
| Metrics |
cvssV4_0
|