Description
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| tensorflow | tensorflow | < 1.15.4, >= 2.0.0, < 2.0.3, >= 2.1.0, < 2.1.2, >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 15.2 | tensorflow2 +3 | 2.1.2-lp152.7.3.1 | openSUSE-SU-2020:1766-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | tensorflow | < 1.15.4 | 1.15.4 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow | < 1.15.4 · >= 2.0.0, < 2.0.3 · >= 2.1.0, < 2.1.2 · >= 2.2.0, < 2.2.1 · >= 2.3.0, < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-128 |
| PyPI | tensorflow-cpu | < 1.15.4 | 1.15.4 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-cpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-cpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-cpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-cpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-cpu | < 1.15.4 · >= 2.0.0, < 2.0.3 · >= 2.1.0, < 2.1.2 · >= 2.2.0, < 2.2.1 · >= 2.3.0, < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-285 |
| PyPI | tensorflow-gpu | < 1.15.4 | 1.15.4 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-gpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-gpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-gpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-gpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-g7p5-5759-qv46 |
| PyPI | tensorflow-gpu | < 1.15.4 · >= 2.0.0, < 2.0.3 · >= 2.1.0, < 2.1.2 · >= 2.2.0, < 2.2.1 · >= 2.3.0, < 2.3.1 | 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 | PYSEC-2020-320 |
Advisories 1
- openSUSE-SU-2020:1766-1 Security update for tensorflow2 SUSE / openSUSE Security Updates · Feb 4, 2026