Advisory

GHSA-57wx-m983-2f88

Also known as: BIT-tensorflow-2021-41208, CVE-2021-41208, PYSEC-2021-400, PYSEC-2021-617, PYSEC-2021-815

Summary

Incomplete validation in boosted trees code

Details

Impact
The code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing nullptrs or via CHECK-failures) as well as abuse undefined behavior (binding references to nullptrs). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call.

Note: Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. Instead, please use the downstream TensorFlow Decision Forests project which is newer and supports more features. We will deprecate TensorFlow's boosted trees APIs in subsequent releases.

Patches
We have patched the issue in GitHub commit 5c8c9a8bfe750f9743d0c859bae112060b216f5c.

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

Critical Basis: The source's own band: CRITICAL

Dates

Published
2021-11-10 19:37 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