CVE-2021-41208
Description
TensorFlow is an open source platform for machine learning. In affected versions the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). 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. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. We will deprecate TensorFlow's boosted trees APIs in subsequent releases. 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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Arch Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Fixed | 2.6.1-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-gpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-gpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-cpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-cpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-cpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-gpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow | <5c8c9a8bfe750f9743d0c859bae112060b216f5c||>=2.7.0rc0,<2.7.0 | 5c8c9a8bfe750f9743d0c859bae112060b216f5c |
| PyPI | tensorflow-gpu | <5c8c9a8bfe750f9743d0c859bae112060b216f5c||>=2.7.0rc0,<2.7.0 | 5c8c9a8bfe750f9743d0c859bae112060b216f5c |
| PyPI | tensorflow-cpu | <5c8c9a8bfe750f9743d0c859bae112060b216f5c||>=2.7.0rc0,<2.7.0 | 5c8c9a8bfe750f9743d0c859bae112060b216f5c |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88
- https://nvd.nist.gov/vuln/detail/CVE-2021-41208
- https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-617.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-815.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-400.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-41208
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.