What is the severity of CVE-2022-35937?

The severity of CVE-2022-35937 is classified as medium due to the potential for out-of-bounds memory reads.

How do I fix CVE-2022-35937?

To fix CVE-2022-35937, users should update TensorFlow to the latest stable version that addresses this vulnerability.

Which versions of TensorFlow are affected by CVE-2022-35937?

CVE-2022-35937 affects TensorFlow versions from 2.7.0 to 2.7.2, 2.8.0 to 2.8.1, 2.9.0 to 2.9.1, and specific release candidates of 2.10.

What is the impact of CVE-2022-35937 on TensorFlow applications?

The impact of CVE-2022-35937 includes potential application crashes and exposure to out-of-bounds memory access, which may lead to data corruption or unauthorized information leakage.

Are there workarounds for CVE-2022-35937 if an update cannot be applied?

Currently, there are no specific workarounds recommended for CVE-2022-35937; applying an update is the best course of action.

Vulnerability/
CVE-2022-35937

critical

9.1

CWE

125

16/9/2022

3/8/2024

CVE-2022-35937: OOB read in `Gather_nd` op in TensorFlow Lite

First published: Fri Sep 16 2022(Updated: )

TensorFlow is an open source platform for machine learning. The `GatherNd` function takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read is triggered. This issue has been patched in GitHub commit 595a65a3e224a0362d7e68c2213acfc2b499a196. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
Google TensorFlow	>=2.7.0<2.7.2
Google TensorFlow	>=2.8.0<2.8.1
Google TensorFlow	>=2.9.0<2.9.1
Google TensorFlow	=2.10-rc0
Google TensorFlow	=2.10-rc1
Google TensorFlow	=2.10-rc2
Google TensorFlow	=2.10-rc3

Remedy

https://github.com/tensorflow/tensorflow/commit/595a65a3e224a0362d7e68c2213acfc2b499a196

Remedy

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pxrw-j2fv-hx3h

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-35937?
The severity of CVE-2022-35937 is classified as medium due to the potential for out-of-bounds memory reads.
How do I fix CVE-2022-35937?
To fix CVE-2022-35937, users should update TensorFlow to the latest stable version that addresses this vulnerability.
Which versions of TensorFlow are affected by CVE-2022-35937?
CVE-2022-35937 affects TensorFlow versions from 2.7.0 to 2.7.2, 2.8.0 to 2.8.1, 2.9.0 to 2.9.1, and specific release candidates of 2.10.
What is the impact of CVE-2022-35937 on TensorFlow applications?
The impact of CVE-2022-35937 includes potential application crashes and exposure to out-of-bounds memory access, which may lead to data corruption or unauthorized information leakage.
Are there workarounds for CVE-2022-35937 if an update cannot be applied?
Currently, there are no specific workarounds recommended for CVE-2022-35937; applying an update is the best course of action.

collector/nvd-index
agent/type
agent/remedy
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/author
agent/weakness
agent/title
agent/severity
agent/first-publish-date
agent/event
agent/description
agent/tags
agent/source
vendor/google
canonical/google tensorflow
version/google tensorflow/2.7.0
version/google tensorflow/2.8.0
version/google tensorflow/2.9.0
version/google tensorflow/2.10-rc0
version/google tensorflow/2.10-rc1
version/google tensorflow/2.10-rc2
version/google tensorflow/2.10-rc3

Frequently Asked Questions

What is the severity of CVE-2022-35937?
The severity of CVE-2022-35937 is classified as medium due to the potential for out-of-bounds memory reads.
How do I fix CVE-2022-35937?
To fix CVE-2022-35937, users should update TensorFlow to the latest stable version that addresses this vulnerability.
Which versions of TensorFlow are affected by CVE-2022-35937?
CVE-2022-35937 affects TensorFlow versions from 2.7.0 to 2.7.2, 2.8.0 to 2.8.1, 2.9.0 to 2.9.1, and specific release candidates of 2.10.
What is the impact of CVE-2022-35937 on TensorFlow applications?
The impact of CVE-2022-35937 includes potential application crashes and exposure to out-of-bounds memory access, which may lead to data corruption or unauthorized information leakage.
Are there workarounds for CVE-2022-35937 if an update cannot be applied?
Currently, there are no specific workarounds recommended for CVE-2022-35937; applying an update is the best course of action.

CVE-2022-35937: OOB read in `Gather_nd` op in TensorFlow Lite

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-35937?

How do I fix CVE-2022-35937?

Which versions of TensorFlow are affected by CVE-2022-35937?

What is the impact of CVE-2022-35937 on TensorFlow applications?

Are there workarounds for CVE-2022-35937 if an update cannot be applied?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2022-35937?

How do I fix CVE-2022-35937?

Which versions of TensorFlow are affected by CVE-2022-35937?

What is the impact of CVE-2022-35937 on TensorFlow applications?

Are there workarounds for CVE-2022-35937 if an update cannot be applied?