Process crash via unchecked output-size multiplication
Published May 20, 2022 · Updated Apr 22, 2025
Integer overflow in Google TensorFlow before 2.6.4 and selected 2.7 through 2.9 releases allows local users to crash a process. SpaceToBatchND multiplies the input batch size by attacker-controlled block dimensions without overflow checking, then uses the wrapped result to allocate the output tensor. Reachability requires control of operation arguments; the bounded consequence is a CHECK assertion failure and process crash, not data access or modification.
Summary
What happened
Integer overflow in Google TensorFlow before 2.6.4 and selected 2.7 through 2.9 releases allows local users to crash a process. SpaceToBatchND multiplies the input batch size by attacker-controlled block dimensions without overflow checking, then uses the wrapped result to allocate the output tensor. Reachability requires control of operation arguments; the bounded consequence is a CHECK assertion failure and process crash, not data access or modification.
The record
- CVE
- CVE-2022-29203
- Published
- May 20, 2022
- Updated
- Apr 22, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.6.4
- Affected versionversion=>= 2.7.0rc0, < 2.7.2
- Affected versionversion=>= 2.8.0rc0, < 2.8.1
- Affected versionversion=>= 2.9.0rc0, < 2.9.0
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 SpaceToBatchND crash proof of conceptproof 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