nday
CVE-2020-15197 GHSA-qc53-44cj-vfvx

Denial of Service in Tensorflow

tensorflow / tensorflow

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

network
AV:N in CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H (CVSS 3.1) from the CNA GitHub_M
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H (CVSS 3.1) from the CNA GitHub_M
TensorFlow
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflow
AI / ML
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflowthe product type of TensorFlow in nday's product registry
open-source library / framework
affected products in the CVE record: tensorflow · tensorflowCPE names NVD's analysts give as vulnerable: a:google:tensorflowthe product type of TensorFlow in nday's product registry
stage
DIS
disclosed
cvss
6.3 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2020-09-25T18:40Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In Tensorflow before version 2.3.1, the 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. However, 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. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Event log

+DISdisclosed

CVE record published by GitHub_M. CVSS 6.3, medium.

src cvelist · nday , bulk import · raw
{
  "id": 223370,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2020-15197",
  "occurred_at": "2020-09-25T18:40:31Z",
  "observed_at": "2026-11-13T05:37:10.972872Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H",
      "version": "3.1",
      "base_score": 6.3,
      "base_severity": "MEDIUM"
    },
    "state": "PUBLISHED",
    "date_published": "2020-09-25T18:40:31.000Z",
    "assigner_short_name": "GitHub_M"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.