pysec-2020-301
Vulnerability from pysec
Published
2020-12-10 23:15
Modified
2021-12-09 06:34
Details
In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.
Aliases
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "tensorflow-cpu", "purl": "pkg:pypi/tensorflow-cpu" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "14755416e364f17fb1870882fa778c7fec7f16e3" } ], "repo": "https://github.com/tensorflow/tensorflow", "type": "GIT" }, { "events": [ { "introduced": "0" }, { "fixed": "1.15.5" }, { "introduced": "2.0.0" }, { "fixed": "2.0.4" }, { "introduced": "2.1.0" }, { "fixed": "2.1.3" }, { "introduced": "2.2.0" }, { "fixed": "2.2.2" }, { "introduced": "2.3.0" }, { "fixed": "2.3.2" } ], "type": "ECOSYSTEM" } ], "versions": [ "1.15.0", "2.1.0", "2.1.1", "2.1.2", "2.2.0", "2.2.1", "2.3.0", "2.3.1" ] } ], "aliases": [ "CVE-2020-26270", "GHSA-m648-33qf-v3gp" ], "details": "In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.", "id": "PYSEC-2020-301", "modified": "2021-12-09T06:34:44.825248Z", "published": "2020-12-10T23:15:00Z", "references": [ { "type": "ADVISORY", "url": "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m648-33qf-v3gp" }, { "type": "FIX", "url": "https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.