Undefined behavior via empty k tensor
Published Aug 12, 2021 · Updated Aug 4, 2024
CWE-824 in Google TensorFlow versions before 2.3.4, 2.4.3, or 2.5.1 allows local users to trigger undefined behavior in MatrixDiagV* operations. The kernels accept scalar or vector k tensors without checking element count, then dereference the first element of an empty tensor and bind a reference to null. Exploitation requires local ability to invoke the raw operation; the documented consequence is undefined behavior that can affect process integrity or availability.
Summary
What happened
CWE-824 in Google TensorFlow versions before 2.3.4, 2.4.3, or 2.5.1 allows local users to trigger undefined behavior in MatrixDiagV* operations. The kernels accept scalar or vector k tensors without checking element count, then dereference the first element of an empty tensor and bind a reference to null. Exploitation requires local ability to invoke the raw operation; the documented consequence is undefined behavior that can affect process integrity or availability.
The record
- CVE
- CVE-2021-37657
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-824
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.4
- Affected versionversion=>= 2.4.0, < 2.4.3
- Affected versionversion=>= 2.5.0, < 2.5.1
What conditions does exploitation require?
What is affected?
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