Process crash via non-scalar Bincount size
Published Feb 3, 2022 · Updated May 5, 2025
Denial of service in TensorFlow allows remote authenticated users to crash a serving process by submitting malformed Bincount inputs. Dense, Sparse, and Ragged Bincount paths treat the size tensor as a scalar without first rejecting a non-scalar rank, causing a CHECK failure during later output allocation. Exploitation requires control of tensors supplied to an exposed TensorFlow workload; the demonstrated consequence is process termination without data disclosure or modification.
Summary
What happened
Denial of service in TensorFlow allows remote authenticated users to crash a serving process by submitting malformed Bincount inputs. Dense, Sparse, and Ragged Bincount paths treat the size tensor as a scalar without first rejecting a non-scalar rank, causing a CHECK failure during later output allocation. Exploitation requires control of tensors supplied to an exposed TensorFlow workload; the demonstrated consequence is process termination without data disclosure or modification.
The record
- CVE
- CVE-2022-21737
- Published
- Feb 3, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, CWE-754, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- TensorFlow DenseBincount crash triggerproof 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