Advisory

PYSEC-2020-299

Also known as: BIT-tensorflow-2020-26268, CVE-2020-26268, GHSA-hhvc-g5hv-48c6, PYSEC-2020-255, PYSEC-2020-334

Summary

The record has no summary.

Details

In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Severity

Not rated by the source.

Dates

Published
2020-12-10 23:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 1.15.5, introduced 2.0.0, fixed 2.0.4, introduced 2.1.0, fixed 2.1.3, introduced 2.2.0, fixed 2.2.2, introduced 2.3.0, fixed 2.3.2 (ecosystem)

Fixed versions

1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2

Fix

  • Fixed version 1.15.5
    pip install --upgrade tensorflow-cpu==1.15.5
  • Fixed version 2.0.4
    pip install --upgrade tensorflow-cpu==2.0.4
  • Fixed version 2.1.3
    pip install --upgrade tensorflow-cpu==2.1.3
  • Fixed version 2.2.2
    pip install --upgrade tensorflow-cpu==2.2.2
  • Fixed version 2.3.2
    pip install --upgrade tensorflow-cpu==2.3.2

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