Improper Input Validation Affecting tensorflow/tensorflow package, versions [,2.3.1)


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.26% (66th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-TENSORFLOWTENSORFLOW-2333431
  • published12 Jan 2022
  • disclosed25 Sept 2020
  • creditUnknown

Introduced: 25 Sep 2020

CVE-2020-15199  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

Upgrade tensorflow/tensorflow to version 2.3.1 or higher.

Overview

Affected versions of this package are vulnerable to Improper Input Validation. In Tensorflow before version 2.3.1, the RaggedCountSparseOutput does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the splits tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since BatchedMap is equivalent to a vector, it needs to have at least one element to not be nullptr. If user passes a splits tensor that is empty or has exactly one element, we get a SIGABRT signal raised by the operating system. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

CVSS Scores

version 3.1