Undefined behavior via unchecked right-hand tensor
Published Feb 4, 2022 · Updated Apr 22, 2025
Uninitialized data use in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to trigger undefined behavior. AssignOp checks whether its destination tensor is initialized but copies from the right-hand tensor without first checking its initialization state. Reachability requires graph execution to invoke AssignOp with an uninitialized right-hand tensor; observed outcomes include null-pointer bindings.
Summary
What happened
Uninitialized data use in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to trigger undefined behavior. AssignOp checks whether its destination tensor is initialized but copies from the right-hand tensor without first checking its initialization state. Reachability requires graph execution to invoke AssignOp with an uninitialized right-hand tensor; observed outcomes include null-pointer bindings.
The record
- CVE
- CVE-2022-23573
- Published
- Feb 4, 2022
- Updated
- Apr 22, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 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.5.3
- Affected versionversion=>= 2.6.0, < 2.6.3
- Affected versionversion=>= 2.7.0, < 2.7.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
No public exploit references are available in this record.
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