Service interruption via premature crypto context cleanup
Published May 21, 2021 · Updated Aug 3, 2024
Memory leak in Trusted Firmware-M 1.3.0 and earlier allows remote attackers to exhaust the Crypto service via failed multipart operations. The failing update or finish path clears tfm_crypto_operation_s before the underlying library's abort() runs, erasing the context and allocation pointers needed to release resources. All configurations are affected, but exhaustion requires a library that dynamically allocates operation memory; repeated failures can disable Crypto and dependent services.
Summary
What happened
Memory leak in Trusted Firmware-M 1.3.0 and earlier allows remote attackers to exhaust the Crypto service via failed multipart operations. The failing update or finish path clears tfm_crypto_operation_s before the underlying library's abort() runs, erasing the context and allocation pointers needed to release resources. All configurations are affected, but exhaustion requires a library that dynamically allocates operation memory; repeated failures can disable Crypto and dependent services.
The record
- CVE
- CVE-2021-32032
- Published
- May 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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