CVE-2021-37690 Use after free and segfault in shape inference functions in TensorFlow

Medium 6.6 Published Updated

Attackers can trigger a use-after-free vulnerability in TensorFlow shape inference functions, causing a segmentation fault and denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2021-37690?

CVE-2021-37690 is a medium-severity use after free vulnerability in Google Tensorflow, published on 12 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

TensorFlow is an end-to-end open source platform for machine learning. In affected versions when running shape functions, some functions (such as `MutableHashTableShape`) produce extra output information in the form of a `ShapeAndType` struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. `ShapeRefiner` is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. We have patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1. 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.

Weakness: CWE-416

Which versions are affected by CVE-2021-37690?

22 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

PackageAffectedFixed in
tensorflow BitnamiFrom 2.3.02.3.4, 2.4.3, 2.5.1
tensorflow PyPIAll versions2.3.4
tensorflow PyPIAll versions2.3.4
tensorflow PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow PyPIFrom 2.4.02.4.3
tensorflow PyPIFrom 2.4.02.4.3
16 more packages
tensorflow PyPIFrom 2.5.02.5.1
tensorflow PyPIFrom 2.5.02.5.1
tensorflow-cpu PyPIAll versions2.3.4
tensorflow-cpu PyPIAll versions2.3.4
tensorflow-cpu PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow-cpu PyPIFrom 2.4.02.4.3
tensorflow-cpu PyPIFrom 2.4.02.4.3
tensorflow-cpu PyPIFrom 2.5.02.5.1
tensorflow-cpu PyPIFrom 2.5.02.5.1
tensorflow-gpu PyPIAll versions2.3.4
tensorflow-gpu PyPIAll versions2.3.4
tensorflow-gpu PyPIFrom 2.3.02.3.4, 2.4.3
tensorflow-gpu PyPIFrom 2.4.02.4.3
tensorflow-gpu PyPIFrom 2.4.02.4.3
tensorflow-gpu PyPIFrom 2.5.02.5.1
tensorflow-gpu PyPIFrom 2.5.02.5.1

Products include Google Tensorflow.

How do I fix CVE-2021-37690?

Upgrade tensorflow to a fixed version for your release line: 2.3.4, 2.4.3 or 2.5.1.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2021-37690 being exploited?

There is no known exploitation of CVE-2021-37690 in the wild and no public exploit code.

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-37690, GHSA-3hxh-8cp2-g4hg, PYSEC-2021-312, PYSEC-2021-603, PYSEC-2021-801.

Is CVE-2021-37690 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free