Advisory

GHSA-4f99-p9c2-3j8x

Also known as: BIT-tensorflow-2021-41219, CVE-2021-41219, PYSEC-2021-411, PYSEC-2021-628, PYSEC-2021-826

Summary

Undefined behavior via nullptr reference binding in sparse matrix multiplication

Details

Impact
The code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to nullptr:

import tensorflow as tf
  
tf.raw_ops.SparseMatMul(
  a=[[1.0,1.0,1.0]],
  b=[[],[],[]],
  transpose_a=False,
  transpose_b=False,
  a_is_sparse=False, 
  b_is_sparse=True)

This occurs whenever the dimensions of a or b are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.

Patches
We have patched the issue in GitHub commit e6cf28c72ba2eb949ca950d834dd6d66bb01cfae.

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 by members of the Aivul Team from Qihoo 360.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2021-11-10 18:51 UTC
Modified
2026-07-08 06:28 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