tensorflow
Affected
- introduced
0, fixed2.7.2(ecosystem)
Fixed versions
2.7.2
Fix
- Fixed version
2.7.2pip install --upgrade tensorflow==2.7.2
Advisory
Also known as: BIT-tensorflow-2022-35940, CVE-2022-35940, PYSEC-2026-1047, PYSEC-2026-3259, PYSEC-2026-3381
TensorFlow vulnerable to Int overflow in RaggedRangeOp
Impact
The `RaggedRangOp` function takes an argument limits that is eventually used to construct a TensorShape as an int64. If limits is a very large float, it can overflow when converted to an int64. This triggers an InvalidArgument but also throws an abort signal that crashes the program.
import tensorflow as tf
tf.raw_ops.RaggedRange(starts=[1.1,0.1],limits=[10.0,1e20],deltas=[1,1])
Patches
We have patched the issue in GitHub commit 37cefa91bee4eace55715eeef43720b958a01192.
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.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by Jingyi Shi.
Medium Basis: The source's own band: MODERATE
0, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow==2.9.10, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow-cpu==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow-cpu==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow-cpu==2.9.10, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow-gpu==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow-gpu==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow-gpu==2.9.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0