Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-21725

Division by zero in Tensorflow

Overview

Published
3 Feb 2022
Modified
17 Jun 2026
Medium CVE
4 Registry packages
2 OS packages
1 Linux distributions
Yes Fix available

Description

Tensorflow is an Open Source Machine Learning Framework. The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-369

Affected packages · 4

Packages affected by CVE-2022-21725
EcosystemPackageVulnerableFixed in
Bitnami tensorflow <2.5.3>=2.6.0, <2.6.3>=2.7.0, <2.7.1 2.5.32.6.32.7.1
PyPI tensorflow <2.5.3>=2.6.0, <2.6.3>=2.7.0, <2.7.1 2.5.32.6.32.7.1
PyPI tensorflow-cpu <2.5.3>=2.6.0, <2.6.3>=2.7.0, <2.7.1 2.5.32.6.32.7.1
PyPI tensorflow-gpu <2.5.3>=2.6.0, <2.6.3>=2.7.0, <2.7.1 2.5.32.6.32.7.1

Open a package to see all its vulnerabilities.

Operating systems · 1 fix

openSUSE 1 release · 1 package

fixed 1
tensorflow-lite
openSUSE fixes for CVE-2022-21725
ReleasePackageFixed inAdvisory
Tumbleweed tensorflow-lite +1 2.9.1-1.1 openSUSE-SU-2024:12116-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.