8.4

CVE-2021-37639: google tensorflow NULL Pointer Dereference

CVSS: 8.4v3.1HighModified
AliasesGHSA-gh6x-4whr-2qv4BIT-tensorflow-2021-37639PYSEC-2021-261
Published 12-08-2021Last modified 04-08-2024

Vulnerability summary

CVE-2021-37639 is a high (CVSS 8.4) NULL Pointer Dereference vulnerability in google tensorflow. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 6.3% of scored vulnerabilities.

Overall risk
34/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.4/10
010
High · v3.1 (CVE.org)
EPSS score
0.17%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 1

Timeline

  1. 12-08-2021
    PublishedVulnerability first disclosed.
  2. 04-08-2024
    Last modifiedVulnerability information updated.

Description

TensorFlow is an end-to-end open source platform for machine learning. When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read. We have patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622. 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.

CVSS metrics

5 scores · 3 sources · 3 versions

EPSS trend

Probability

0.17%

Chance of exploitation in the next 30 days

Percentile

6%

Versus all other CVEs

30-day change

0.00 pp

From 0.17% on 18-09-2026

18-09-202618-10-2026
EPSS score
0.17%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

PyPI3 products
  • tensorflow< 2.3.4 | ≥ 2.5.0, < 2.5.1 | < 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622 | ≥ 2.4.0, < 2.4.3
  • tensorflow-cpu< 2.3.4 | ≥ 2.5.0, < 2.5.1 | < 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622 | ≥ 2.4.0, < 2.4.3
  • tensorflow-gpu< 2.3.4 | ≥ 2.5.0, < 2.5.1 | < 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622 | ≥ 2.4.0, < 2.4.3
Google1 product
  • tensorflow≥ 2.3.0, < 2.3.4 | ≥ 2.4.0, < 2.4.3 | 2.5.0 | 2.6.0:rc0 | 2.6.0:rc1 | 2.6.0:rc2
Tensorflow1 product
  • tensorflow≥ 2.5.0, < 2.5.1 | ≥ 2.4.0, < 2.4.3 | < 2.3.4

3 vendors · 5 products

References

7 links