Skip to content
TensorFlowGHSA-w5gh-2wr2-pm6g

Denial of Service in Tensorflow

High9.0CVE-2020-15206 · Published Sep 25, 2020 · updated Jul 8, 2026

### Impact 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. We have added fixes to this in 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. ### Patches We have patched the issue in adf095206f25471e864a8e63a0f1caef53a0e3a6 and will release patch releases for all versions between 1.15 and 2.3. Patch releases for versions between 1.15 and 2.1 will also contain cherry-picks of f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and ques...

GitHub advisory

Affected versions

PackageAffectedFixed in
tensorflow
PyPI
< 1.15.41.15.4
>= 2.0.0, < 2.0.32.0.3
>= 2.1.0, < 2.1.22.1.2
>= 2.2.0, < 2.2.12.2.1
>= 2.3.0, < 2.3.12.3.1
Details and references

### Impact 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. We have added fixes to this in 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. ### Patches We have patched the issue in adf095206f25471e864a8e63a0f1caef53a0e3a6 and will release patch releases for all versions between 1.15 and 2.3. Patch releases for versions between 1.15 and 2.1 will also contain cherry-picks of f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Shuaike Dong, from Alipay Tian Qian Security Lab && Lab for Applied Security Research, CUHK.

CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Severity from
GitHub (reviewed advisory)
Weakness
CWE-20
Also known as
BIT-tensorflow-2020-15206, CVE-2020-15206, PYSEC-2020-129, PYSEC-2020-286, PYSEC-2020-321

More TensorFlow advisories

All TensorFlow
Advisory
Out of bounds access in tensorflow-lite
Critical8.1Sep 25, 2020
Out of bounds write in tensorflow-lite
Critical8.1Sep 25, 2020
Denial of service in tensorflow-lite
Medium4.0Sep 25, 2020
Segmentation fault in tensorflow-lite
High6.5Sep 25, 2020
Out of bounds access in tensorflow-lite
Medium4.8Sep 25, 2020
Null pointer dereference in tensorflow-lite
High5.9Sep 25, 2020

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.