Secure-world code execution via unchecked mailbox pointers
Published Oct 9, 2024 · Updated Oct 10, 2024
Memory corruption in Trusted Firmware-M 1.6.0 through 2.1.0 allows attackers to execute code in secure firmware via mailbox messages. The mailbox_direct_reply routine writes output-vector lengths through unvalidated caller-supplied list pointers even after a PSA call fails. Exploitation requires an NSPE client on a platform using the standard tfm_spe_mailbox dispatcher and can overwrite secure memory and seize control flow.
Summary
What happened
Memory corruption in Trusted Firmware-M 1.6.0 through 2.1.0 allows attackers to execute code in secure firmware via mailbox messages. The mailbox_direct_reply routine writes output-vector lengths through unvalidated caller-supplied list pointers even after a PSA call fails. Exploitation requires an NSPE client on a platform using the standard tfm_spe_mailbox dispatcher and can overwrite secure memory and seize control flow.
The record
- CVE
- CVE-2024-45746
- Published
- Oct 9, 2024
- Updated
- Oct 10, 2024
- Vendor
- Trusted Firmware
- Product
- Trusted Firmware-M
- Classifications
- CWE-120, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 10, 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=1.6.0 <=2.1.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