Undefined behavior via empty input_splits tensor
Published Aug 12, 2021 · Updated Aug 4, 2024
Improper pointer access in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to trigger undefined behavior. UnicodeEncode reads the first dimension of input_splits before checking whether the tensor is empty, binding a reference to a null pointer. Local code must invoke the operation with an empty input_splits tensor; the published record does not establish a more specific consequence than undefined behavior.
Summary
What happened
Improper pointer access in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to trigger undefined behavior. UnicodeEncode reads the first dimension of input_splits before checking whether the tensor is empty, binding a reference to a null pointer. Local code must invoke the operation with an empty input_splits tensor; the published record does not establish a more specific consequence than undefined behavior.
The record
- CVE
- CVE-2021-37667
- 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?
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
- UnicodeEncode empty-input reproducerproof of concept · demonstrated
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