Insecure temporary file in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. 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. We have patched the issue in several commits, replacing `mktemp` with the safer `mkstemp`/`mkdtemp` functions, according to the usage pattern. Users are advised to upgrade as soon as possible.
From the CVE record · GitHub_M
TensorFlow utilities and libraries use `tempfile.mktemp` in ways that leave a race between choosing a temporary filename and creating the file or directory. A different local process can create it during that interval. The input does not specify authentication requirements or user interaction.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu in versions <2.5.3, >=2.6.0 <2.6.3, or >=2.7.0 <2.7.1.