CVE-2021-37671 json
Reference binding to nullptr in map operations in TensorFlow
published 2021-08-12 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-37671 , EUVD-2021-0397 , GHSA-qr82-2c78-4m8h , PYSEC-2021-293 , PYSEC-2021-584 , PYSEC-2021-782
- cvss
- 7.8
- 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 6%
- 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 undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty. We have patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac. 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
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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-824 Access of Uninitialized Pointer
References
-
github.com
/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-qr82-2c78-4m8h
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-37671
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-584.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-782.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-293.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-37671
- GitHub Advisory GHSA-qr82-2c78-4m8h
- NVD CVE-2021-37671
- OSV BIT-tensorflow-2021-37671
- OSV PYSEC-2021-293
- OSV PYSEC-2021-584
- OSV PYSEC-2021-782
Fencer Vulns 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.