Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. 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.
References
Link | Resource |
---|---|
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2 | Patch Third Party Advisory |
https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/kernels/assign_op.h#L30-L143 | Exploit Third Party Advisory |
https://github.com/tensorflow/tensorflow/commit/ef1d027be116f25e25bb94a60da491c2cf55bd0b | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2022-02-04 15:15
Updated : 2022-02-10 07:32
NVD link : CVE-2022-23573
Mitre link : CVE-2022-23573
JSON object : View
CWE
CWE-908
Use of Uninitialized Resource
Products Affected
- tensorflow