GHSA-h6gw-r52c-724r json
NULL Pointer Dereference and Access of Uninitialized Pointer in TensorFlow
published 4y ago modified last yr.
- cvss
- 9.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
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.
Patch / fix
- pypi tensorflow 2.5.3, 2.6.3, 2.7.1
- pypi tensorflow-cpu 2.5.3, 2.6.3, 2.7.1
- pypi tensorflow-gpu 2.5.3, 2.6.3, 2.7.1
Is GHSA-h6gw-r52c-724r in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
| pypi | tensorflow-cpu | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
| pypi | tensorflow-gpu | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
Classification
References
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88
web
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-h6gw-r52c-724r
web
-
github.com
/tensorflow/tensorflow
package
-
github.com
/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/sta
web
Sources
- GitHub Advisory GHSA-h6gw-r52c-724r
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.