Skip to content

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

Moderate severity GitHub Reviewed Published Jan 7, 2025 in matrix-org/matrix-rust-sdk • Updated Jan 7, 2025

Package

cargo matrix-sdk-crypto (Rust)

Affected versions

< 0.8.0

Patched versions

0.8.0

Description

Impact

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.

Patches

matrix-sdk-crypto 0.8.0 adds a new VerificationLevel::VerificationViolation enum variant which indicates that a previously verified identity has been changed.

Workarounds

N/A

References

References

@dkasak dkasak published to matrix-org/matrix-rust-sdk Jan 7, 2025
Published to the GitHub Advisory Database Jan 7, 2025
Reviewed Jan 7, 2025
Published by the National Vulnerability Database Jan 7, 2025
Last updated Jan 7, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Weaknesses

CVE ID

CVE-2024-52813

GHSA ID

GHSA-r5vf-wf4h-82gg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.