Process crash via overflowed batch count allocation
Published Feb 3, 2022 · Updated May 5, 2025
Integer overflow in affected TensorFlow releases allows remote authenticated users to crash a process through SparseCountSparseOutput. In count_ops.cc, SparseCount derives a signed int num_batches from dense_shape and uses it to size a BatchedMap without rejecting overflowed or nonpositive values. Exposure is limited to 2.5.2 and earlier, 2.6.0 through 2.6.2, and 2.7.0 when an authenticated caller can provide a crafted dense_shape; the consequence is process termination only.
Summary
What happened
Integer overflow in affected TensorFlow releases allows remote authenticated users to crash a process through SparseCountSparseOutput. In count_ops.cc, SparseCount derives a signed int num_batches from dense_shape and uses it to size a BatchedMap without rejecting overflowed or nonpositive values. Exposure is limited to 2.5.2 and earlier, 2.6.0 through 2.6.2, and 2.7.0 when an authenticated caller can provide a crafted dense_shape; the consequence is process termination only.
The record
- CVE
- CVE-2022-21738
- Published
- Feb 3, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499
- 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.
Public exploit references
- SparseCountSparseOutput crash reproducerproof 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