Advisory

GHSA-r4c4-5fpq-56wg

Also known as: BIT-tensorflow-2021-37664, CVE-2021-37664, PYSEC-2021-286, PYSEC-2021-577, PYSEC-2021-775

Summary

Heap OOB in boosted trees

Details

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

import tensorflow as tf

tf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(
  node_id_range=[0,10],
  stats_summary_indices=[[1, 2, 3, 0x1000000]],
  stats_summary_values=[1.0],
  stats_summary_shape=[1,1,1,1],
  l1=l2=[1.0],
  tree_complexity=[0.5],
  min_node_weight=[1.0],
  logits_dimension=3,
  split_type='inequality')                                                                                                                                                                                                                                                                

The implementation needs to validate that each value in stats_summary_indices is in range.

Patches
We have patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378.

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

High Basis: The source's own band: HIGH

Dates

Published
2021-08-25 14:42 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