PYSEC-2020-130: tensorflow fixed in 2d88f470dea2671b430884260f3626b1fe99830a, 2.3.1, 2.2.1 and 3 more

PYSEC-2020-130 PUBLISHED CVSS 9.300000190734863 CRITICAL

Record from OSV · Published September 25, 2020

tensorflow is fixed in 2d88f470dea2671b430884260f3626b1fe99830a, 2.3.1, 2.2.1 and 3 more (PyPI)

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

Package	Ecosystem	Fixed in
tensorflow	PyPI	2d88f470dea2671b430884260f3626b1fe99830a, 2.3.1, 2.2.1, 2.1.2, 2.0.3, 1.15.4

Risk scores

CVSS 4.0

9.300000190734863

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected products

Vendor	Product	Versions
PyPI	tensorflow	0, 1.2.0, 2.0.0

Timeline

Sep 25, 2020 CVE Published

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln PYSEC-2020-130
vulnetix vdb fixes PYSEC-2020-130

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/PYSEC-2020-130/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →