CVE-2021-29520: TensorFlow - Missing Validation in Conv3DBackprop Operations

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
High
Not published

CVE-2021-29520: Heap buffer overflow in Conv3DBackprop*. Affects tensorflow across 4 version ranges.

< 2.1.4 >= 2.2.0, < 2.2.3 >= 2.3.0, < 2.3.3 >= 2.4.0, < 2.4.2

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-29520 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem for building and deploying machine learning models. TensorFlow is widely used in various industries and research domains due to its flexibility and scalability. However, a vulnerability has been identified in TensorFlow that affects versions 0 and 2.1.4 to 2.4.2. This vulnerability is related to missing validation between arguments in tf.raw_ops.Conv3DBackprop* operations, which can lead to heap buffer overflows.

Vulnerability Detail

The vulnerability arises from the lack of validation between the input, filter_sizes, and out_backprop tensors in tf.raw_ops.Conv3DBackprop* operations. The implementation assumes that these tensors have the same shape and are accessed in parallel. However, if the shapes of these tensors differ, it can result in a heap buffer overflow. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial of service. The impact of this vulnerability is considered high.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.1.4 2.1.4
  • >= 2.2.0, < 2.2.3 2.2.3
  • >= 2.3.0, < 2.3.3 2.3.3
  • >= 2.4.0, < 2.4.2 2.4.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, TensorFlow versions 0 and 2.1.4 to 2.4.2 are vulnerable to a heap buffer overflow due to missing validation in tf.raw_ops.Conv3DBackprop* operations. This vulnerability can be mitigated by upgrading to TensorFlow 2.5.0 or one of the backported versions. If you require further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides a comprehensive ecosystem for building and deploying machine learning models.

The impact of this vulnerability is considered high. It can lead to heap buffer overflows, allowing an attacker to execute arbitrary code or cause a denial of service.

Versions 0 and 2.1.4 to 2.4.2 of TensorFlow are affected by this vulnerability.

To fix this vulnerability, it is recommended to upgrade to TensorFlow 2.5.0 or later. Alternatively, you can upgrade to one of the backported versions: 2.1.4, 2.2.3, 2.3.3, or 2.4.2.

No specific workaround has been mentioned for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.1.4 2.1.4
  • >= 2.2.0, < 2.2.3 2.2.3
  • >= 2.3.0, < 2.3.3 2.3.3
  • >= 2.4.0, < 2.4.2 2.4.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback