Process crash via non-numeric tensor type confusion
Published May 14, 2021 · Updated Aug 3, 2024
Type confusion in Google TensorFlow affected releases allows local users to crash a process by passing a non-numeric tensor. In ndarray_tensor.cc, PyArrayDescr_to_TF_DataType passes a null NumPy descriptor fields pointer to PyDict_Next during Python-to-C++ conversion. Executing TensorFlow code locally and supplying an incompatible tensor type is required; the documented consequence is a null-pointer crash of the invoking process.
Summary
What happened
Type confusion in Google TensorFlow affected releases allows local users to crash a process by passing a non-numeric tensor. In ndarray_tensor.cc, PyArrayDescr_to_TF_DataType passes a null NumPy descriptor fields pointer to PyDict_Next during Python-to-C++ conversion. Executing TensorFlow code locally and supplying an incompatible tensor type is required; the documented consequence is a null-pointer crash of the invoking process.
The record
- CVE
- CVE-2021-29513
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, CWE-843
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 14, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.4
- Affected versionversion=>= 2.2.0, < 2.2.3
- Affected versionversion=>= 2.3.0, < 2.3.3
- Affected versionversion=>= 2.4.0, < 2.4.2
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
- Upstream TensorFlow reproduction examplesproof 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