Process crash via unchecked SetSize tensor rank
Published Sep 16, 2022 · Updated Apr 23, 2025
Reachable assertion in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash the host process. SparseTensorFromContext calls the tensor vector accessor on set_shape without checking that the input has rank one, so a scalar or multidimensional tensor triggers a fatal check. Exploitation requires attacker-controlled tensor arguments to reach SetSize through a consuming application, and the abort interrupts that application without reported data compromise.
Summary
What happened
Reachable assertion in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash the host process. SparseTensorFromContext calls the tensor vector accessor on set_shape without checking that the input has rank one, so a scalar or multidimensional tensor triggers a fatal check. Exploitation requires attacker-controlled tensor arguments to reach SetSize through a consuming application, and the abort interrupts that application without reported data compromise.
The record
- CVE
- CVE-2022-35993
- Published
- Sep 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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.7.2
- Affected versionversion=>= 2.8.0, < 2.8.1
- Affected versionversion=>= 2.9.0, < 2.9.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
- SetSize malformed-shape proof of conceptproof of concept · unverified
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