False identity trust via unchecked own verification
Published Jul 18, 2024 · Updated Aug 2, 2024
Improper authentication in matrix-sdk-crypto before 0.7.2 allows remote attackers controlling a homeserver to make identities appear trusted. UserIdentity::is_verified() checks only whether the local user's identity signed the other identity and omits own_identity.is_verified(), so an unverified trust root still yields true. Exposure requires application code to use this public method for a sensitive trust decision; the crate does not call the method internally.
Summary
What happened
Improper authentication in matrix-sdk-crypto before 0.7.2 allows remote attackers controlling a homeserver to make identities appear trusted. UserIdentity::is_verified() checks only whether the local user's identity signed the other identity and omits own_identity.is_verified(), so an unverified trust root still yields true. Exposure requires application code to use this public method for a sensitive trust decision; the crate does not call the method internally.
The record
- CVE
- CVE-2024-40648
- Published
- Jul 18, 2024
- Updated
- Aug 2, 2024
- Vendor
- The Matrix.org Foundation
- Product
- matrix-rust-sdk
- Classifications
- CWE-287
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.7.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo