Read the docs
TI-2022-26476 Aliases GHSA-h6gw-r52c-724r

NULL Pointer Dereference and Access of Uninitialized Pointer in TensorFlow

Priority LOW 38CWE-476Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Denial of service
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-476.

Summary

### Impact The [code for boosted trees in TensorFlow](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/stats_ops.cc) 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 `nullptr`s 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](https://github.com/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](https://github.com/tensorflow/decision-forests), while guaranteeing that known vulnerabilities are fixed. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) 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.

Why it matters now

Fix Fixed tensorflow (PyPI): 2.5.3, 2.6.3, 2.7.1tensorflow-cpu (PyPI): 2.5.3, 2.6.3, 2.7.1+1 more product

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—tensorflow (PyPI)before 2.5.32.5.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow (PyPI)2.6.0 to before 2.6.32.6.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow (PyPI)2.7.0 to before 2.7.12.7.1Patch availableGHSA-h6gw-r52c-724r
—tensorflow-cpu (PyPI)before 2.5.32.5.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow-cpu (PyPI)2.6.0 to before 2.6.32.6.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow-cpu (PyPI)2.7.0 to before 2.7.12.7.1Patch availableGHSA-h6gw-r52c-724r
—tensorflow-gpu (PyPI)before 2.5.32.5.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow-gpu (PyPI)2.6.0 to before 2.6.32.6.3Patch availableGHSA-h6gw-r52c-724r
—tensorflow-gpu (PyPI)2.7.0 to before 2.7.12.7.1Patch availableGHSA-h6gw-r52c-724r
  • tensorflow (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-cpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-cpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-cpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-gpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-gpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-h6gw-r52c-724r
  • tensorflow-gpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-h6gw-r52c-724r

Remediation

  • Fix · GHSA-h6gw-r52c-724r tensorflow (PyPI) Fixed in 2.5.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow (PyPI) Fixed in 2.6.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow (PyPI) Fixed in 2.7.1 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-cpu (PyPI) Fixed in 2.5.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-cpu (PyPI) Fixed in 2.6.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-cpu (PyPI) Fixed in 2.7.1 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-gpu (PyPI) Fixed in 2.5.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-gpu (PyPI) Fixed in 2.6.3 Advisory →
  • Fix · GHSA-h6gw-r52c-724r tensorflow-gpu (PyPI) Fixed in 2.7.1 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-h6gw-r52c-724r

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences