{"id":"CVE-2020-15197","aliases":["GHSA-qc53-44cj-vfvx","BIT-tensorflow-2020-15197","PYSEC-2020-120","PYSEC-2020-277","PYSEC-2020-312"],"title":"Denial of Service in Tensorflow","summary":"Denial of Service in Tensorflow","severity":"medium","cvss":6.3,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H","vendor":"tensorflow","product":"tensorflow","ecosystem":"pip","affected":["tensorflow >= 2.3.0, < 2.3.1","tensorflow-cpu >= 2.3.0, < 2.3.1","tensorflow-gpu >= 2.3.0, < 2.3.1"],"patched":["tensorflow 2.3.1","tensorflow-cpu 2.3.1","tensorflow-gpu 2.3.1"],"published":"2020-09-25","updated":"2026-07-08","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-qc53-44cj-vfvx","references":[{"url":"https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qc53-44cj-vfvx"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15197"},{"url":"https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-277.yaml"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-312.yaml"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-120.yaml"},{"url":"https://github.com/tensorflow/tensorflow"},{"url":"https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1"}],"tags":["osv","pip"],"epss":0.00726,"epssPercentile":0.52695,"ingestedAt":"2026-07-08T18:25:52.396Z","slug":"CVE-2020-15197","body":"## Overview\n\n### Impact\nThe `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix:\nhttps://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L185\n\nHowever, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor.\n\n### Patches\nWe have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.\n\nWe recommend users to upgrade to TensorFlow 2.3.1.\n\n### For more information\nPlease 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.\n\n### Attribution\nThis vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)\n\n## Affected packages\n\n- `tensorflow >= 2.3.0, < 2.3.1`\n- `tensorflow-cpu >= 2.3.0, < 2.3.1`\n- `tensorflow-gpu >= 2.3.0, < 2.3.1`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `tensorflow 2.3.1`\n- `tensorflow-cpu 2.3.1`\n- `tensorflow-gpu 2.3.1`","depth":"sunlit","depthScore":35,"depthScoreParts":{"impact":34.7,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}