Vulnerability in Google Tensorflow
CVE-2021-41201
TensorFlow is an open source platform for machine learning. In affeced versions during execution, `EinsumHelper::ParseEquation()` is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to `true` and never assigns `false`. This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.002, 16.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow — versions 2.6.0
- Tensorflow — versions >= 2.6.0, < 2.6.1, >= 2.5.0, < 2.5.2, < 2.4.4
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (adwisatya/SnykVulndb, ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm (Exploit, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6 (Patch, Third Party Advisory)