CVE-2020-26271
Description
In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.
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.4.0-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <1.15.5 | 1.15.5 |
| PyPI | tensorflow | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow-cpu | <1.15.5 | 1.15.5 |
| PyPI | tensorflow-cpu | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow-cpu | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow-cpu | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow-cpu | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow-gpu | <1.15.5 | 1.15.5 |
| PyPI | tensorflow-gpu | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow-gpu | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow-gpu | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow-gpu | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow | <0cc38aaa4064fd9e79101994ce9872c6d91f816b||>=2.3.0,<2.3.2 | 0cc38aaa4064fd9e79101994ce9872c6d91f816b |
| PyPI | tensorflow-cpu | <0cc38aaa4064fd9e79101994ce9872c6d91f816b||>=2.3.0,<2.3.2 | 0cc38aaa4064fd9e79101994ce9872c6d91f816b |
| PyPI | tensorflow-gpu | <0cc38aaa4064fd9e79101994ce9872c6d91f816b||>=2.3.0,<2.3.2 | 0cc38aaa4064fd9e79101994ce9872c6d91f816b |
References
- https://security.archlinux.org/ASA-202012-22
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q263-fvxm-m5mw
- https://nvd.nist.gov/vuln/detail/CVE-2020-26271
- https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-302.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-337.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-257.yaml
- https://security-tracker.debian.org/tracker/CVE-2020-26271
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.