CVE-2021-37646
Description
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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.5.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.3.4 | 2.3.4 |
| PyPI | tensorflow | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow-cpu | <2.3.4 | 2.3.4 |
| PyPI | tensorflow-cpu | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow-cpu | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow-gpu | <2.3.4 | 2.3.4 |
| PyPI | tensorflow-gpu | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow-gpu | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow-cpu | <c283e542a3f422420cfdb332414543b62fc4e4a5||>=2.4.0,<2.4.3 | c283e542a3f422420cfdb332414543b62fc4e4a5 |
| PyPI | tensorflow | <c283e542a3f422420cfdb332414543b62fc4e4a5||>=2.4.0,<2.4.3 | c283e542a3f422420cfdb332414543b62fc4e4a5 |
| PyPI | tensorflow-gpu | <c283e542a3f422420cfdb332414543b62fc4e4a5||>=2.4.0,<2.4.3 | c283e542a3f422420cfdb332414543b62fc4e4a5 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6jh-7gv5-28vg
- https://nvd.nist.gov/vuln/detail/CVE-2021-37646
- https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-559.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-757.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-268.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-37646
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.