Undefined behavior 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.3.0 · < 2.3.1< 2.2.1≥ 2.3.0rc0 · < 2.3.1
|
| tensorflow-gpu PyPI |
|
|
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
From the CVE record · GitHub_M
TensorFlow's `dlpack.to_dlpack` does not properly check an error status after receiving an invalid argument. Subsequent code can reference null pointers, causing undefined behavior. The input does not specify whether an attacker can trigger this remotely or whether authentication or user interaction is required.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu running versions before 2.2.1 or versions from 2.3.0rc0 before 2.3.1.