Process crash via unchecked sparse-tensor row index
Published May 14, 2021 · Updated Aug 3, 2024
An out-of-bounds heap write in Google TensorFlow crashes the executing process when malformed sparse-tensor indices reach the conversion routine. SparseTensorToCSRSparseMatrixCPUFunctor increments csr_row_ptr at a computed row position without first verifying that the position falls inside the allocated array. Exploitation requires local control of the indices passed to the conversion; the documented consequence is termination of the affected process.
Summary
What happened
An out-of-bounds heap write in Google TensorFlow crashes the executing process when malformed sparse-tensor indices reach the conversion routine. SparseTensorToCSRSparseMatrixCPUFunctor increments csr_row_ptr at a computed row position without first verifying that the position falls inside the allocated array. Exploitation requires local control of the indices passed to the conversion; the documented consequence is termination of the affected process.
The record
- CVE
- CVE-2021-29545
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-131, T1499.004
- Attack vector
- local
- Privileges
- authenticated
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?
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 SparseTensorToCSRSparseMatrix crash 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