Advisory

PYSEC-2020-119

Also known as: BIT-tensorflow-2020-15196, CVE-2020-15196, GHSA-pg59-2f92-5cph, PYSEC-2020-276, PYSEC-2020-311

Summary

The record has no summary.

Details

In Tensorflow version 2.3.0, 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. In the sparse and ragged count weights are still accessed in parallel with the data. 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. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

Severity

Not rated by the source.

Dates

Published
2020-09-25 19:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.3.1 (ecosystem)

Fixed versions

2.3.1

Fix

  • Fixed version 2.3.1
    pip install --upgrade tensorflow==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: PyPA Advisory Database · CC BY 4.0

Sources & licences