Advisory

GHSA-cq76-mxrc-vchh

Also known as: BIT-tensorflow-2021-41195, CVE-2021-41195, PYSEC-2021-842, PYSEC-2021-844, PYSEC-2021-846

Summary

Crash in tf.math.segment_* operations

Details

Impact
The implementation of tf.math.segment_* operations results in a CHECK-fail related abort (and denial of service) if a segment id in segment_ids is large.

import tensorflow as tf

tf.math.segment_max(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_min(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_mean(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])    
tf.math.segment_sum(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_prod(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])

This is similar to CVE-2021-29584 (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using `AddDim`. However, if the number of elements in the tensor overflows an int64_t value, AddDim results in a CHECK failure which provokes a std::abort. Instead, code should use `AddDimWithStatus`.

Patches
We have patched the issue in GitHub commit e9c81c1e1a9cd8dd31f4e83676cab61b60658429 (merging #51733).

The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.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.

Attribution
This vulnerability has been reported externally via a GitHub issue.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-11-10 19:36 UTC
Modified
2026-07-08 06:29 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

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

tensorflow

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

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

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

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

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

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

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

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

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