Local memory disclosure via unchecked tensor index
Published Aug 12, 2021 · Updated Aug 4, 2024
Out-of-bounds read in TensorFlow before 2.3.4 allows local users to read memory via raw tensor restoration APIs. The Restore and RestoreSlice kernels index tensor lists using the user-controlled preferred_shard value without verifying that enough tensor names exist, causing heap out-of-bounds reads or null-pointer dereferences. Exploitation requires local access to invoke these raw APIs, and consequences are memory disclosure or process interruption rather than a network compromise.
Summary
What happened
Out-of-bounds read in TensorFlow before 2.3.4 allows local users to read memory via raw tensor restoration APIs. The Restore and RestoreSlice kernels index tensor lists using the user-controlled preferred_shard value without verifying that enough tensor names exist, causing heap out-of-bounds reads or null-pointer dereferences. Exploitation requires local access to invoke these raw APIs, and consequences are memory disclosure or process interruption rather than a network compromise.
The record
- CVE
- CVE-2021-37639
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
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.
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