Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2020-15202

9.0 · CRITICAL

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments.

Published Sep 25, 2020CWE-197EPSS 1.29%

Overview

CVE-2020-15202 is a critical-severity vulnerability. It was published on September 25, 2020 and has a CVSS 3.1 base score of 9.0 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Reflists.opensuse.org/opensuse-security-announce/2020-10/msg00065.htmlGitHubgithub.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832GitHubgithub.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575GitHubgithub.com/tensorflow/tensorflow/releases/tag/v2.3.1GitHubgithub.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4Reflists.opensuse.org/opensuse-security-announce/2020-10/msg00065.htmlGitHubgithub.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832GitHubgithub.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575GitHubgithub.com/tensorflow/tensorflow/releases/tag/v2.3.1GitHubgithub.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4

How CyberStrike helps

Frequently asked questions

What is CVE-2020-15202?

CVE-2020-15202 is a critical-severity vulnerability. It was published on September 25, 2020 and has a CVSS 3.1 base score of 9.0 (CRITICAL).

How severe is CVE-2020-15202?

This vulnerability has a CVSS 3.1 base score of 9.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2020-15202?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2020-15202?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2020-15202 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2020

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999