CVE-2021-41201
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Arch Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Fixed | 2.6.1-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-cpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-cpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-cpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-gpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-gpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-gpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow | <f09caa532b6e1ac8d2aa61b7832c78c5b79300c6||>=2.7.0rc0,<2.7.0 | f09caa532b6e1ac8d2aa61b7832c78c5b79300c6 |
| PyPI | tensorflow-cpu | <f09caa532b6e1ac8d2aa61b7832c78c5b79300c6||>=2.7.0rc0,<2.7.0 | f09caa532b6e1ac8d2aa61b7832c78c5b79300c6 |
| PyPI | tensorflow-gpu | <f09caa532b6e1ac8d2aa61b7832c78c5b79300c6||>=2.7.0rc0,<2.7.0 | f09caa532b6e1ac8d2aa61b7832c78c5b79300c6 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm
- https://nvd.nist.gov/vuln/detail/CVE-2021-41201
- https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-611.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-809.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-394.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-41201
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.