Advisory

GHSA-h6gw-r52c-724r

Also known as: None

Summary

NULL Pointer Dereference and Access of Uninitialized Pointer in TensorFlow

Details

Impact
The code for boosted trees in TensorFlow is still missing validation. This allows malicious users to read and write outside of bounds of heap allocated data as well as trigger denial of service (via dereferencing nullptrs or via CHECK-failures).

This follows after CVE-2021-41208 where these APIs were still vulnerable to multiple security issues.

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.

These APIs are now deprecated in TensorFlow 2.8. We will remove TensorFlow's boosted trees APIs in subsequent releases.

Patches
We have patched the known issues in multiple GitHub commits.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

This should allow users to use existing boosted trees APIs for a while until they migrate to TensorFlow Decision Forests, while guaranteeing that known vulnerabilities are fixed.

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
These vulnerabilities have been reported by Yu Tian of Qihoo 360 AIVul Team and Faysal Hossain Shezan from University of Virginia. Some of the issues have been discovered internally after a careful audit of the APIs.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2022-02-09 23:38 UTC
Modified
2024-12-05 05:33 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.5.3 (ecosystem)

Fixed versions

2.5.3

Fix

  • Fixed version 2.5.3
    pip install --upgrade tensorflow==2.5.3

tensorflow

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.3 (ecosystem)

Fixed versions

2.6.3

Fix

  • Fixed version 2.6.3
    pip install --upgrade tensorflow==2.6.3

tensorflow

PyPI · All systems

Affected

  • introduced 2.7.0, fixed 2.7.1 (ecosystem)

Fixed versions

2.7.1

Fix

  • Fixed version 2.7.1
    pip install --upgrade tensorflow==2.7.1

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.5.3 (ecosystem)

Fixed versions

2.5.3

Fix

  • Fixed version 2.5.3
    pip install --upgrade tensorflow-cpu==2.5.3

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.3 (ecosystem)

Fixed versions

2.6.3

Fix

  • Fixed version 2.6.3
    pip install --upgrade tensorflow-cpu==2.6.3

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.7.0, fixed 2.7.1 (ecosystem)

Fixed versions

2.7.1

Fix

  • Fixed version 2.7.1
    pip install --upgrade tensorflow-cpu==2.7.1

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.5.3 (ecosystem)

Fixed versions

2.5.3

Fix

  • Fixed version 2.5.3
    pip install --upgrade tensorflow-gpu==2.5.3

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.3 (ecosystem)

Fixed versions

2.6.3

Fix

  • Fixed version 2.6.3
    pip install --upgrade tensorflow-gpu==2.6.3

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.7.0, fixed 2.7.1 (ecosystem)

Fixed versions

2.7.1

Fix

  • Fixed version 2.7.1
    pip install --upgrade tensorflow-gpu==2.7.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