CVE-2020-26269 Heap out of bounds read in filesystem glob matching in TensorFlow
An attacker can trigger a heap out-of-bounds read in TensorFlow's glob matching, potentially causing crashes or leaking memory.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-26269?
CVE-2020-26269 is a high-severity memory corruption vulnerability in Google Tensorflow, published on 10 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.
Weakness: CWE-125
Which versions are affected by CVE-2020-26269?
10 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tensorflow Bitnami | From 2.4.0-rc0 | 2.4.0, 2.4.0, 2.4.0, 2.4.0, 2.4.0 |
tensorflow PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow-cpu PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow-cpu PyPI | From 2.4.0rc0 | 2.4.0 |
4 more packages
tensorflow-cpu PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow-gpu PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow-gpu PyPI | From 2.4.0rc0 | 2.4.0 |
tensorflow-gpu PyPI | From 2.4.0rc0 | 2.4.0 |
Products include Google Tensorflow.
How do I fix CVE-2020-26269?
Upgrade tensorflow to 2.4.0 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-26269 being exploited?
There is no known exploitation of CVE-2020-26269 in the wild and no public exploit code.
Other vulnerabilities in Google Tensorflow
- CVE-2023-25668 TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation
- CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow
- CVE-2021-37678 Arbitrary code execution due to YAML deserialization
- CVE-2021-35958 Path traversal in n/a
- CVE-2020-15202 Integer truncation in Shard API usage
Sources
Also known as BIT-tensorflow-2020-26269, GHSA-9jjw-hf72-3mxw, PYSEC-2020-141, PYSEC-2020-300, PYSEC-2020-335.