Advisory

GHSA-pg59-2f92-5cph

Also known as: BIT-tensorflow-2020-15196, CVE-2020-15196, PYSEC-2020-119, PYSEC-2020-276, PYSEC-2020-311

Summary

Heap buffer overflow in Tensorflow

Details

Impact
The SparseCountSparseOutput and RaggedCountSparseOutput implementations don't validate that the weights tensor has the same shape as the data. The check exists for DenseCountSparseOutput, where both tensors are fully specified:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L110-L117

In the sparse and ragged count weights are still accessed in parallel with the data:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L199-L201

But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights.

Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.

We recommend users to upgrade to TensorFlow 2.3.1.

For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution
This vulnerability is a variant of GHSA-p5f8-gfw5-33w4

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-09-25 18:28 UTC
Modified
2026-07-08 05:59 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 2.3.0, fixed 2.3.1 (ecosystem)

Fixed versions

2.3.1

Fix

  • Fixed version 2.3.1
    pip install --upgrade tensorflow==2.3.1

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.3.0, fixed 2.3.1 (ecosystem)

Fixed versions

2.3.1

Fix

  • Fixed version 2.3.1
    pip install --upgrade tensorflow-cpu==2.3.1

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.3.0, fixed 2.3.1 (ecosystem)

Fixed versions

2.3.1

Fix

  • Fixed version 2.3.1
    pip install --upgrade tensorflow-gpu==2.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences