CVE-2022-23568: TensorFlow: integer overflow DoS in sparse tensor ops
MEDIUM PoC AVAILABLE CISA: TRACK*Any TensorFlow deployment on versions 2.5.x–2.7.x that processes sparse tensor inputs from authenticated users is vulnerable to remote crash via integer overflow in AddManySparseToTensorsMap. Patch immediately to TF 2.8.0, 2.7.1, 2.6.3, or 2.5.3. No effective workaround exists beyond restricting access to affected inference endpoints.
Risk Assessment
Medium risk in practice despite easy exploitability. CVSS 6.5: network-reachable, low complexity, only requires low-privilege credentials—any authenticated user can trigger the crash. Impact is strictly availability (no data exfiltration or code execution). Risk escalates for public-facing model serving APIs where user-submitted sparse tensors are processed without upstream input sanitization, and for deployments lacking process auto-restart.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| tensorflow | pip | — | No patch |
Do you use tensorflow? You're affected.
Severity & Risk
Attack Surface
Recommended Action
5 steps-
Upgrade to TF 2.8.0, 2.7.1, 2.6.3, or 2.5.3 (patches: commits a68f680 and b51b82f on the TF repo).
-
If immediate patching is blocked, add input validation middleware to reject SparseTensor inputs with dimension values exceeding expected bounds before they reach TF kernels.
-
Configure process supervisors (systemd RestartOnFailure, k8s liveness probes) to auto-restart TF serving processes on crash.
-
Monitor for unexpected TF process exits and spike in 5xx errors from inference endpoints as detection signals.
-
Audit all API endpoints that accept sparse tensor inputs from external or low-trust callers and apply authentication + rate limiting.
CISA SSVC Assessment
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2022-23568?
Any TensorFlow deployment on versions 2.5.x–2.7.x that processes sparse tensor inputs from authenticated users is vulnerable to remote crash via integer overflow in AddManySparseToTensorsMap. Patch immediately to TF 2.8.0, 2.7.1, 2.6.3, or 2.5.3. No effective workaround exists beyond restricting access to affected inference endpoints.
Is CVE-2022-23568 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2022-23568, increasing the risk of exploitation.
How to fix CVE-2022-23568?
1. Upgrade to TF 2.8.0, 2.7.1, 2.6.3, or 2.5.3 (patches: commits a68f680 and b51b82f on the TF repo). 2. If immediate patching is blocked, add input validation middleware to reject SparseTensor inputs with dimension values exceeding expected bounds before they reach TF kernels. 3. Configure process supervisors (systemd RestartOnFailure, k8s liveness probes) to auto-restart TF serving processes on crash. 4. Monitor for unexpected TF process exits and spike in 5xx errors from inference endpoints as detection signals. 5. Audit all API endpoints that accept sparse tensor inputs from external or low-trust callers and apply authentication + rate limiting.
What systems are affected by CVE-2022-23568?
This vulnerability affects the following AI/ML architecture patterns: model serving, training pipelines, inference.
What is the CVSS score for CVE-2022-23568?
CVE-2022-23568 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.30%.
Technical Details
NVD Description
Tensorflow is an Open Source Machine Learning Framework. The implementation of `AddManySparseToTensorsMap` is vulnerable to an integer overflow which results in a `CHECK`-fail when building new `TensorShape` objects (so, an assert failure based denial of service). We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
Exploitation Scenario
An attacker with a valid low-privilege API credential to a TF Serving endpoint submits a crafted inference request containing a SparseTensor with artificially inflated shape dimensions. When AddManySparseToTensorsMap processes the input, the integer overflow during TensorShape construction triggers a CHECK-fail assertion, immediately crashing the TF serving process. In a Kubernetes deployment without liveness probes, this takes the inference pod offline. By automating a stream of such requests from a single authenticated session, the attacker achieves persistent DoS against the model serving infrastructure with minimal cost and zero specialized ML expertise beyond knowing the target framework.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H References
- github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc Exploit 3rd Party
- github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8 Patch 3rd Party
- github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c Patch 3rd Party
- github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2 Patch 3rd Party
Timeline
Related Vulnerabilities
CVE-2020-15196 9.9 TensorFlow: heap OOB read in sparse/ragged count ops
Same package: tensorflow CVE-2020-15205 9.8 TensorFlow: heap overflow in StringNGrams, ASLR bypass
Same package: tensorflow CVE-2020-15208 9.8 TFLite: OOB read/write via tensor dimension mismatch
Same package: tensorflow CVE-2019-16778 9.8 TensorFlow: heap overflow in UnsortedSegmentSum op
Same package: tensorflow CVE-2022-23587 9.8 TensorFlow: integer overflow in Grappler enables RCE
Same package: tensorflow
AI Threat Alert