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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.
| Link | Tags |
|---|---|
| https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | third party advisory |
| https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8 | third party advisory patch |
| https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr | third party advisory exploit |
| http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html | mailing list third party advisory vendor advisory |