Advisory

GHSA-3hxh-8cp2-g4hg

Also known as: BIT-tensorflow-2021-37690, CVE-2021-37690, PYSEC-2021-312, PYSEC-2021-603, PYSEC-2021-801

Summary

Use after free and segfault in shape inference functions

Details

Impact
When running shape functions, some functions (such as MutableHashTableShape) produce extra output information in the form of a ShapeAndType struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault.

ShapeRefiner is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types.

Patches
We have patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1.

The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-08-25 14:39 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.3.4 (ecosystem)

Fixed versions

2.3.4

Fix

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

tensorflow

PyPI · All systems

Affected

  • introduced 2.4.0, fixed 2.4.3 (ecosystem)

Fixed versions

2.4.3

Fix

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

tensorflow

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.1 (ecosystem)

Fixed versions

2.5.1

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.3.4 (ecosystem)

Fixed versions

2.3.4

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.4.0, fixed 2.4.3 (ecosystem)

Fixed versions

2.4.3

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.1 (ecosystem)

Fixed versions

2.5.1

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.3.4 (ecosystem)

Fixed versions

2.3.4

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.4.0, fixed 2.4.3 (ecosystem)

Fixed versions

2.4.3

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.1 (ecosystem)

Fixed versions

2.5.1

Fix

  • Fixed version 2.5.1
    pip install --upgrade tensorflow-gpu==2.5.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