PYSEC-2021-228
Vulnerability from pysec - Published: 2021-05-14 20:15 - Updated: 2021-08-27 03:22TensorFlow is an end-to-end open source platform for machine learning. TFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls. For example, the While implementation(https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the Eval function for the other and this quickly exhaust all stack space. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. 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.
| Name | purl | tensorflow | pkg:pypi/tensorflow |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "tensorflow",
"purl": "pkg:pypi/tensorflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "9c1dc920d8ffb4893d6c9d27d1f039607b326743"
},
{
"fixed": "c6173f5fe66cdbab74f4f869311fe6aae2ba35f4"
}
],
"repo": "https://github.com/tensorflow/tensorflow",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.1.4"
},
{
"introduced": "2.2.0"
},
{
"fixed": "2.2.3"
},
{
"introduced": "2.3.0"
},
{
"fixed": "2.3.3"
},
{
"introduced": "2.4.0"
},
{
"fixed": "2.4.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.12.0",
"0.12.0rc0",
"0.12.0rc1",
"0.12.1",
"1.0.0",
"1.0.1",
"1.1.0",
"1.1.0rc0",
"1.1.0rc1",
"1.1.0rc2",
"1.10.0",
"1.10.0rc0",
"1.10.0rc1",
"1.10.1",
"1.11.0",
"1.11.0rc0",
"1.11.0rc1",
"1.11.0rc2",
"1.12.0",
"1.12.0rc0",
"1.12.0rc1",
"1.12.0rc2",
"1.12.2",
"1.12.3",
"1.13.0rc0",
"1.13.0rc1",
"1.13.0rc2",
"1.13.1",
"1.13.2",
"1.14.0",
"1.14.0rc0",
"1.14.0rc1",
"1.15.0",
"1.15.0rc0",
"1.15.0rc1",
"1.15.0rc2",
"1.15.0rc3",
"1.15.2",
"1.15.3",
"1.15.4",
"1.15.5",
"1.2.0",
"1.2.0rc0",
"1.2.0rc1",
"1.2.0rc2",
"1.2.1",
"1.3.0",
"1.3.0rc0",
"1.3.0rc1",
"1.3.0rc2",
"1.4.0",
"1.4.0rc0",
"1.4.0rc1",
"1.4.1",
"1.5.0",
"1.5.0rc0",
"1.5.0rc1",
"1.5.1",
"1.6.0",
"1.6.0rc0",
"1.6.0rc1",
"1.7.0",
"1.7.0rc0",
"1.7.0rc1",
"1.7.1",
"1.8.0",
"1.8.0rc0",
"1.8.0rc1",
"1.9.0",
"1.9.0rc0",
"1.9.0rc1",
"1.9.0rc2",
"2.0.0",
"2.0.0a0",
"2.0.0b0",
"2.0.0b1",
"2.0.0rc0",
"2.0.0rc1",
"2.0.0rc2",
"2.0.1",
"2.0.2",
"2.0.3",
"2.0.4",
"2.1.0",
"2.1.0rc0",
"2.1.0rc1",
"2.1.0rc2",
"2.1.1",
"2.1.2",
"2.1.3",
"2.2.0",
"2.2.1",
"2.2.2",
"2.3.0",
"2.3.1",
"2.3.2",
"2.4.0",
"2.4.1"
]
}
],
"aliases": [
"CVE-2021-29591",
"GHSA-cwv3-863g-39vx"
],
"details": "TensorFlow is an end-to-end open source platform for machine learning. TFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls. For example, the `While` implementation(https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. 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.",
"id": "PYSEC-2021-228",
"modified": "2021-08-27T03:22:37.582991Z",
"published": "2021-05-14T20:15:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cwv3-863g-39vx"
},
{
"type": "FIX",
"url": "https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743"
},
{
"type": "FIX",
"url": "https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.