CVE-2022-21734: `CHECK`-failures in Tensorflow
6.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.43492%
CWE
Published
2/10/2022
Updated
11/13/2024
KEV Status
No
Technology
Python
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
tensorflow | pip | < 2.5.3 | 2.5.3 |
tensorflow | pip | >= 2.6.0, < 2.6.3 | 2.6.3 |
tensorflow | pip | = 2.7.0 | 2.7.1 |
tensorflow-cpu | pip | < 2.5.3 | 2.5.3 |
tensorflow-cpu | pip | >= 2.6.0, < 2.6.3 | 2.6.3 |
tensorflow-cpu | pip | = 2.7.0 | 2.7.1 |
tensorflow-gpu | pip | < 2.5.3 | 2.5.3 |
tensorflow-gpu | pip | >= 2.6.0, < 2.6.3 | 2.6.3 |
tensorflow-gpu | pip | = 2.7.0 | 2.7.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from missing validation in the MapStageOp's Compute function where non-scalar key tensors would trigger CHECK failures. The commit f573155 added an explicit check (OP_REQUIRES) for key tensor scalar validation. The original code in map_stage_op.cc only checked for non-empty keys but not scalar shape. The test cases added in map_stage_op_test.py validate this fix by testing non-scalar key rejection.