Malicious trusted applications via faulted signature result
Published Dec 19, 2022 · Updated Apr 17, 2025
Signature-verification bypass in OP-TEE before 3.20 allows physically proximate attackers to install malicious trusted applications. A precisely timed electromagnetic pulse clears a result register to zero, causing the zero-valued TEE_SUCCESS check to accept an invalid signature. The demonstrated attack requires physical proximity and fault-injection equipment; it exposes no secrets but breaks trusted-application integrity.
Summary
What happened
Signature-verification bypass in OP-TEE before 3.20 allows physically proximate attackers to install malicious trusted applications. A precisely timed electromagnetic pulse clears a result register to zero, causing the zero-valued TEE_SUCCESS check to accept an invalid signature. The demonstrated attack requires physical proximity and fault-injection equipment; it exposes no secrets but breaks trusted-application integrity.
The record
- CVE
- CVE-2022-47549
- Published
- Dec 19, 2022
- Updated
- Apr 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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
- Raspberry Pi 3 electromagnetic glitch attackfunctional · demonstrated
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