7.8

CVE-2021-37648: google tensorflow NULL Pointer Dereference

CVSS: 7.8v3.1HighModified
AliasesGHSA-wp77-4gmm-7cq8BIT-tensorflow-2021-37648PYSEC-2021-270
Published 12-08-2021Last modified 04-08-2024
Open JSON

Vulnerability summary

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

Overall risk
31/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.19%
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
OPENSUSE-SU-2022:10014-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. In affected versions the code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation. We have patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986. 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.19%

Chance of exploitation in the next 30 days

Percentile

8%

Versus all other CVEs

30-day change

0.00 pp

From 0.19% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.19%

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 | < 9728c60e136912a12d99ca56e106b7cce7af5986 | ≥ 2.4.0, < 2.4.3
  • tensorflow-cpu< 2.3.4 | ≥ 2.5.0, < 2.5.1 | < 9728c60e136912a12d99ca56e106b7cce7af5986 | ≥ 2.4.0, < 2.4.3
  • tensorflow-gpu< 2.3.4 | ≥ 2.5.0, < 2.5.1 | < 9728c60e136912a12d99ca56e106b7cce7af5986 | ≥ 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