Advisory

GHSA-9697-98pf-4rw7

Also known as: BIT-tensorflow-2021-37670, CVE-2021-37670, PYSEC-2021-292, PYSEC-2021-583, PYSEC-2021-781

Summary

Heap OOB in UpperBound and LowerBound

Details

Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to tf.raw_ops.UpperBound:

import tensorflow as tf
  
tf.raw_ops.UpperBound(
  sorted_input=[1,2,3],
  values=tf.constant(value=[[0,0,0],[1,1,1],[2,2,2]],dtype=tf.int64),
  out_type=tf.int64)

The implementation does not validate the rank of sorted_input argument:

  void Compute(OpKernelContext* ctx) override {
    const Tensor& sorted_inputs_t = ctx->input(0);
    // ...
    OP_REQUIRES(ctx, sorted_inputs_t.dim_size(0) == values_t.dim_size(0),
                Status(error::INVALID_ARGUMENT,
                       "Leading dim_size of both tensors must match."));
    // ...
    if (output_t->dtype() == DT_INT32) {
      OP_REQUIRES(ctx,
                  FastBoundsCheck(sorted_inputs_t.dim_size(1), ...));
      // ...
    }

As we access the first two dimensions of sorted_inputs_t tensor, it must have rank at least 2.

A similar issue occurs in tf.raw_ops.LowerBound.

Patches
We have patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38.

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-08-25 14:41 UTC
Modified
2026-07-08 06:29 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