Skip to content
Fencer Intel
medium 5.5

CVE-2021-37661 json

Crash caused by integer conversion to unsigned in TensorFlow

published 5y ago modified 2mo ago also BIT-tensorflow-2021-37661 , EUVD-2021-0387 , GHSA-gf88-j2mg-cc82 , PYSEC-2021-283 , PYSEC-2021-574 , PYSEC-2021-772

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. We have patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992. 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.

Patch / fix

  • pypi tensorflow 2.3.4, 2.4.3, 2.5.1
  • pypi tensorflow-cpu 2.3.4, 2.4.3, 2.5.1
  • pypi tensorflow-gpu 2.3.4, 2.4.3, 2.5.1
  • bitnami tensorflow 2.3.4, 2.4.3, 2.5.1
  • google tensorflow 2.3.4, 2.4.3
  • tensorflow2 Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • bazel3.7 Package Hub 15 SP3, openSUSE Leap 15.3 3.7.2-bp153.4.1
  • tensorflow2-lite Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • bazel-skylib1.0.3 Package Hub 15 SP3, openSUSE Leap 15.3 1.0.3-bp153.2.1
  • tensorflow2_2_6_0-gnu-hpc Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • tensorflow2_2_6_0-gnu-openmpi2-hpc Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1

opensuse advisories openSUSE-SU-2022:10014-1

  • tensorflow Arch Linux 2.5.1-1

arch linux advisories AVG-2292

Is CVE-2021-37661 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 Fencer

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
pypi tensorflow-cpu
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
pypi tensorflow-gpu
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
bitnami tensorflow
>=2.3.0, <2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
2.3.4
2.4.3
2.5.1

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-681 Incorrect Conversion between Numeric Types

References

Sources

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.