CVE-2024-52813 matrix-sdk-crypto missing facility to signal rotation of a verified cryptographic identity

Medium 4.3 Published Updated

The matrix-sdk-crypto library fails to notify clients when a verified identity becomes unverified, allowing attackers to bypass security warnings.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2024-52813?

CVE-2024-52813 is a medium-severity vulnerability in matrix-org matrix-rust-sdk, published on 7 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

matrix-rust-sdk is an implementation of a Matrix client-server library in Rust. Versions of the matrix-sdk-crypto Rust crate before 0.8.0 lack a dedicated mechanism to notify that a user's cryptographic identity has changed from a verified to an unverified one, which could cause client applications relying on the SDK to overlook such changes. matrix-sdk-crypto 0.8.0 adds a new VerificationLevel::VerificationViolation enum variant which indicates that a previously verified identity has been changed.

Weakness: CWE-223

Which versions are affected by CVE-2024-52813?

3 open source packages ship an affected version, including matrix-sdk-crypto.

PackageAffectedFixed in
matrix-sdk-crypto crates.ioAll versions0.8.0
matrix-sdk-crypto crates.ioAll versions0.8.0
matrix-sdk-crypto crates.ioFrom 0.0.0-00.8.0
Linux distribution packages (1)
cargo-audit-advisory-db openSUSE:TumbleweedAll versions20250204-1.1

How do I fix CVE-2024-52813?

Upgrade matrix-sdk-crypto to 0.8.0 or later.

Is CVE-2024-52813 being exploited?

There is no known exploitation of CVE-2024-52813 in the wild and no public exploit code.

Sources

Also known as GHSA-r5vf-wf4h-82gg, RUSTSEC-2024-0434, openSUSE-SU-2025:14726-1.

Is CVE-2024-52813 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free