CVE-2022-35966: TensorFlow: DoS via QuantizedAvgPool input validation
HIGH PoC AVAILABLERemotely exploitable crash in TensorFlow's quantized pooling operation — no credentials or user interaction required. Any TF Serving endpoint or inference API that accepts external tensor inputs and uses quantized models is vulnerable to service disruption. Patch to TF 2.10.0, 2.9.1, 2.8.1, or 2.7.2 and add input shape validation at the API boundary.
Risk Assessment
HIGH for organizations running exposed TensorFlow inference endpoints. CVSS 7.5 reflects the worst-case scenario accurately: network-accessible, zero authentication, zero user interaction. The blast radius is limited to availability (no data exfiltration risk), but a single malformed request crashes the TF process. Quantized models are common in edge/mobile deployments and cost-optimized inference fleets — these environments often lack the defensive hardening of core production APIs.
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-
Patch immediately: upgrade to TensorFlow 2.10.0, 2.9.1, 2.8.1, or 2.7.2 — the fix is in commit 7cdf9d4.
-
Add input tensor shape validation at the API gateway layer before ops execution; reject any request where min_input or max_input tensors have rank > 0.
-
Run TF Serving under a process supervisor (systemd, Kubernetes restart policy) to auto-recover from crashes.
-
Audit which inference endpoints use QuantizedAvgPool-containing graphs — grep SavedModel signatures or TFLite flatbuffers.
-
Monitor inference service crash rates and process exit events as a detection signal.
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-35966?
Remotely exploitable crash in TensorFlow's quantized pooling operation — no credentials or user interaction required. Any TF Serving endpoint or inference API that accepts external tensor inputs and uses quantized models is vulnerable to service disruption. Patch to TF 2.10.0, 2.9.1, 2.8.1, or 2.7.2 and add input shape validation at the API boundary.
Is CVE-2022-35966 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2022-35966, increasing the risk of exploitation.
How to fix CVE-2022-35966?
1. Patch immediately: upgrade to TensorFlow 2.10.0, 2.9.1, 2.8.1, or 2.7.2 — the fix is in commit 7cdf9d4. 2. Add input tensor shape validation at the API gateway layer before ops execution; reject any request where min_input or max_input tensors have rank > 0. 3. Run TF Serving under a process supervisor (systemd, Kubernetes restart policy) to auto-recover from crashes. 4. Audit which inference endpoints use QuantizedAvgPool-containing graphs — grep SavedModel signatures or TFLite flatbuffers. 5. Monitor inference service crash rates and process exit events as a detection signal.
What systems are affected by CVE-2022-35966?
This vulnerability affects the following AI/ML architecture patterns: model serving, inference APIs, edge/mobile ML deployment, training pipelines.
What is the CVSS score for CVE-2022-35966?
CVE-2022-35966 has a CVSS v3.1 base score of 7.5 (HIGH). The EPSS exploitation probability is 0.06%.
Technical Details
NVD Description
TensorFlow is an open source platform for machine learning. If `QuantizedAvgPool` is given `min_input` or `max_input` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 7cdf9d4d2083b739ec81cfdace546b0c99f50622. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
Exploitation Scenario
Attacker enumerates TF Serving endpoints via port scanning or API discovery. They craft a gRPC or REST prediction request targeting a model that includes QuantizedAvgPool in its graph, passing a 1D or higher-rank tensor for min_input instead of a scalar. TensorFlow does not validate the tensor rank before passing it to the op, triggering a segfault. The inference process crashes, taking down the serving endpoint. This requires no ML expertise — just knowledge that the target uses TensorFlow and sends quantized model inputs. Attack can be repeated to maintain a persistent DoS against auto-restarting services.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H References
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