PYSEC-2020-128
Vulnerability from pysec - Published: 2020-09-25 19:15 - Updated: 2020-10-29 16:15In 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.
| Name | purl | tensorflow | pkg:pypi/tensorflow |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "tensorflow",
"purl": "pkg:pypi/tensorflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0462de5b544ed4731aa2fb23946ac22c01856b80"
}
],
"repo": "https://github.com/tensorflow/tensorflow",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.15.4"
},
{
"introduced": "2.0.0"
},
{
"fixed": "2.0.3"
},
{
"introduced": "2.1.0"
},
{
"fixed": "2.1.2"
},
{
"introduced": "2.2.0"
},
{
"fixed": "2.2.1"
},
{
"introduced": "2.3.0"
},
{
"fixed": "2.3.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.12.0rc0",
"0.12.0rc1",
"0.12.0",
"0.12.1",
"1.0.0",
"1.0.1",
"1.1.0rc0",
"1.1.0rc1",
"1.1.0rc2",
"1.1.0",
"1.2.0rc0",
"1.2.0rc1",
"1.2.0rc2",
"1.2.0",
"1.2.1",
"1.3.0rc0",
"1.3.0rc1",
"1.3.0rc2",
"1.3.0",
"1.4.0rc0",
"1.4.0rc1",
"1.4.0",
"1.4.1",
"1.5.0rc0",
"1.5.0rc1",
"1.5.0",
"1.5.1",
"1.6.0rc0",
"1.6.0rc1",
"1.6.0",
"1.7.0rc0",
"1.7.0rc1",
"1.7.0",
"1.7.1",
"1.8.0rc0",
"1.8.0rc1",
"1.8.0",
"1.9.0rc0",
"1.9.0rc1",
"1.9.0rc2",
"1.9.0",
"1.10.0rc0",
"1.10.0rc1",
"1.10.0",
"1.10.1",
"1.11.0rc0",
"1.11.0rc1",
"1.11.0rc2",
"1.11.0",
"1.12.0rc0",
"1.12.0rc1",
"1.12.0rc2",
"1.12.0",
"1.12.2",
"1.12.3",
"1.13.0rc0",
"1.13.0rc1",
"1.13.0rc2",
"1.13.1",
"1.13.2",
"1.14.0rc0",
"1.14.0rc1",
"1.14.0",
"1.15.0rc0",
"1.15.0rc1",
"1.15.0rc2",
"1.15.0rc3",
"1.15.0",
"1.15.2",
"1.15.3",
"2.0.0",
"2.0.1",
"2.0.2",
"2.1.0",
"2.1.1",
"2.2.0",
"2.3.0"
]
}
],
"aliases": [
"CVE-2020-15205",
"GHSA-g7p5-5759-qv46"
],
"details": "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.",
"id": "PYSEC-2020-128",
"modified": "2020-10-29T16:15:00Z",
"published": "2020-09-25T19:15:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46"
},
{
"type": "WEB",
"url": "https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1"
},
{
"type": "FIX",
"url": "https://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.