Description
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using `tensorflow-serving` or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d (both going into TensorFlow 2.2.0 and 2.3.0 but not yet backported to earlier versions). However, this was not enough, as #41097 reports a different failure mode. The issue is patched in commit adf095206f25471e864a8e63a0f1caef53a0e3a6, 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-w5gh-2wr2-pm6g |
| PyPI | tensorflow | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-w5gh-2wr2-pm6g |
| 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-129 |
| PyPI | tensorflow-cpu | < 1.15.4 | 1.15.4 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-cpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-cpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-cpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-cpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-w5gh-2wr2-pm6g |
| 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-286 |
| PyPI | tensorflow-gpu | < 1.15.4 | 1.15.4 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-gpu | >= 2.0.0, < 2.0.3 | 2.0.3 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-gpu | >= 2.1.0, < 2.1.2 | 2.1.2 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-gpu | >= 2.2.0, < 2.2.1 | 2.2.1 | GHSA-w5gh-2wr2-pm6g |
| PyPI | tensorflow-gpu | >= 2.3.0, < 2.3.1 | 2.3.1 | GHSA-w5gh-2wr2-pm6g |
| 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-321 |
Advisories 1
- openSUSE-SU-2020:1766-1 Security update for tensorflow2 SUSE / openSUSE Security Updates · Feb 4, 2026