PYSEC-2021-204
Vulnerability from pysec - Published: 2021-05-14 20:15 - Updated: 2021-08-27 03:22
VLAI?
Details
TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in tf.raw_ops.SparseDenseCwiseMul, an attacker can trigger denial of service via CHECK-fails or accesses to outside the bounds of heap allocated data. Since the implementation(https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no constraints between dimensions(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal CHECK assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers. 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.
Impacted products
| Name | purl | tensorflow | pkg:pypi/tensorflow |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "tensorflow",
"purl": "pkg:pypi/tensorflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "7ae2af34087fb4b5c8915279efd03da3b81028bc"
}
],
"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-29567",
"GHSA-wp3c-xw9g-gpcg"
],
"details": "TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in `tf.raw_ops.SparseDenseCwiseMul`, an attacker can trigger denial of service via `CHECK`-fails or accesses to outside the bounds of heap allocated data. Since the implementation(https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no constraints between dimensions(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal `CHECK` assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers. 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.",
"id": "PYSEC-2021-204",
"modified": "2021-08-27T03:22:33.334705Z",
"published": "2021-05-14T20:15:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wp3c-xw9g-gpcg"
},
{
"type": "FIX",
"url": "https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc"
}
]
}
Loading…
Loading…
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.
Loading…
Loading…