Backup private-key disclosure via debug logging
Published May 13, 2024 · Updated Aug 2, 2024
Sensitive-data exposure in Matrix.org matrix-sdk-crypto 0.7.0 allows local users to read a server-side backup private key from debug logs. During OlmMachine initialization, machine.rs re-parses the stored BackupDecryptionKey's Base64 private value as a MegolmV1BackupKey instead of deriving its public key. Exposure requires debug logging and access to the application logs; the bounded consequence is disclosure of the backup private key.
Summary
What happened
Sensitive-data exposure in Matrix.org matrix-sdk-crypto 0.7.0 allows local users to read a server-side backup private key from debug logs. During OlmMachine initialization, machine.rs re-parses the stored BackupDecryptionKey's Base64 private value as a MegolmV1BackupKey instead of deriving its public key. Exposure requires debug logging and access to the application logs; the bounded consequence is disclosure of the backup private key.
The record
- CVE
- CVE-2024-34353
- Published
- May 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Matrix.org
- Product
- matrix-sdk-crypto
- Classifications
- CWE-532, T1552.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 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.0
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