Secure-key disclosure via missing authorization
Published Jan 13, 2022 · Updated Aug 4, 2024
Missing authorization in Trusted Firmware-M 1.4.0 allows remote attackers to read secure keys via crafted key-ID requests. The Crypto service retrieves a key based only on the supplied identifier and does not verify the caller-to-key-owner relationship. Exploitation requires Profile Small with NSPE access to the Crypto service; the documented consequence is unauthorized confidentiality loss without integrity or availability impact.
Summary
What happened
Missing authorization in Trusted Firmware-M 1.4.0 allows remote attackers to read secure keys via crafted key-ID requests. The Crypto service retrieves a key based only on the supplied identifier and does not verify the caller-to-key-owner relationship. Exploitation requires Profile Small with NSPE access to the Crypto service; the documented consequence is unauthorized confidentiality loss without integrity or availability impact.
The record
- CVE
- CVE-2021-40327
- Published
- Jan 13, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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