VDB

PYSEC-2020-337

PYSEC-2020-337 PUBLISHED

Record from OSV · Published December 10, 2020

tensorflow-gpu is fixed in 2.3.2, 2.2.2, 2.1.3 and 3 more (PyPI)

In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Fixed versions

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

PackageEcosystemFixed in
tensorflow-gpuPyPI2.3.2, 2.2.2, 2.1.3, 2.0.4, 1.15.5, 0cc38aaa4064fd9e79101994ce9872c6d91f816b

Affected products

VendorProductVersions
PyPItensorflow-gpu0, 0, 2.1.0

Timeline

  • Dec 10, 2020 CVE Published

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln PYSEC-2020-337
vulnetix vdb fixes PYSEC-2020-337

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-337/fixes/registry"

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

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›