MISFIRE

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

Insecure temporary file in Tensorflow

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

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

How it works, in short

TensorFlow uses tempfile.mktemp, so another process can create the predicted filename first in a race and redirect the subsequent file operation. (Our summary, written by a model. The source text is below.)

Details

Impact

In multiple places, TensorFlow uses tempfile.mktemp to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in mktemp and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness).

In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the mktemp function usage.

Patches

We have patched the issue in several commits, replacing mktemp with the safer mkstemp/mkdtemp functions, according to the usage pattern. 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.

Attribution

This vulnerability has been reported on huntr.dev for one scenario and discovered via variant analysis on other instances.

References

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