MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2022-23573

Uninitialized variable access in Tensorflow

CVE-2022-23573 ยท 2022-02-09 high

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Information exposure
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
EPSS
0.8% chance of exploitation in 30 days

How it works, in short

AssignOp checks only that the destination tensor is initialised, so it copies uninitialised source data into a new tensor, causing undefined behaviour. (Our summary, written by a model. The source text is below.)

Details

Impact

The implementation of AssignOp can result in copying unitialized 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.

### Patches
We have patched the issue in GitHub commit ef1d027be116f25e25bb94a60da491c2cf55bd0b.

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.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

References

Source: GitHub Advisory Database, used under CC BY 4.0.