Process crash via unvalidated protobuf tensor dtype
Published Feb 4, 2022 · Updated Apr 23, 2025
Reachable assertion in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to crash the decoding process. Tensor::FromProto in tensorflow/core/framework/tensor.cc passes an unvalidated proto.dtype() to set_dtype() when a tensor has zero elements or an incomplete shape. A caller must cause an affected process to decode such a crafted TensorProto; the resulting CHECK failure terminates that process.
Summary
What happened
Reachable assertion in Google TensorFlow before 2.5.3, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to crash the decoding process. Tensor::FromProto in tensorflow/core/framework/tensor.cc passes an unvalidated proto.dtype() to set_dtype() when a tensor has zero elements or an incomplete shape. A caller must cause an affected process to decode such a crafted TensorProto; the resulting CHECK failure terminates that process.
The record
- CVE
- CVE-2022-23571
- Published
- Feb 4, 2022
- Updated
- Apr 23, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 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.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.
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