Crash and data leak via uninitialized crypto state
Published Aug 11, 2021 · Updated Aug 5, 2024
Cryptographic state-validation failure in Linaro OP-TEE before 3.7.0 allows attackers to crash the trusted OS and disclose sensitive information. Crypto update and final paths in core/tee/tee_svc_cryp.c process a crypto context without verifying that an initialization function set its state. Exploitation requires an inconsistent or malformed call sequence that reaches those operations before initialization, producing an assertion failure and bounded data exposure.
Summary
What happened
Cryptographic state-validation failure in Linaro OP-TEE before 3.7.0 allows attackers to crash the trusted OS and disclose sensitive information. Crypto update and final paths in core/tee/tee_svc_cryp.c process a crypto context without verifying that an initialization function set its state. Exploitation requires an inconsistent or malformed call sequence that reaches those operations before initialization, producing an assertion failure and bounded data exposure.
The record
- CVE
- CVE-2019-25052
- Published
- Aug 11, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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