Advisory

GHSA-wf5p-c75w-w3wh

Also known as: BIT-tensorflow-2021-37689, CVE-2021-37689, PYSEC-2021-311, PYSEC-2021-602, PYSEC-2021-800

Summary

Null pointer dereference in TFLite MLIR optimizations

Details

Impact
An attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:

This is caused by the MLIR optimization of L2NormalizeReduceAxis operator. The implementation unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements:

bool L2NormalizeReduceAxis(Value sq_op, DenseElementsAttr axis) {
  if (sq_op.getType().cast<ShapedType>().getRank() - 1 ==
          *axis.getValues<int>().begin() ||
      *axis.getValues<int>().begin() == -1) {
      // ...
  }
  // ...
}

Patches
We have patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955.

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.

Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2021-08-25 14:39 UTC
Modified
2026-09-10 03:49 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