CVE-2020-15191
published 2020-09-25CVE-2020-15191: 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…
medium5.3CVSS 3.1
AVNACLPRNUINSUCNINAL
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.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | tensorflow | — | — |
| tensorflow | — | — | |
| tensorflow | — | — | |
| intel | optimization_for_tensorflow | >= 0 < 22e07fb204386768e5bcbea563641ea11f96ceb8 | 22e07fb204386768e5bcbea563641ea11f96ceb8 |
| intel | optimization_for_tensorflow | >= 0 < 2.2.1 | 2.2.1 |
| intel | optimization_for_tensorflow | >= 2.2.0 < 2.2.1 | 2.2.1 |
| intel | optimization_for_tensorflow | >= 2.3.0 < 2.3.1 | 2.3.1 |
| intel | optimization_for_tensorflow | >= 2.3.0rc0 < 2.3.1 | 2.3.1 |
| opensuse | leap | — | — |
| tensorflow | tensorflow | — | — |
| tensorflow | tensorflow | — | — |
OSV
Undefined behavior in Tensorflow
osv·2020-09-25
CVE-2020-15191 [MEDIUM] Undefined behavior in Tensorflow
Undefined behavior in Tensorflow
### Impact
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:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267
Hence, code following these methods will bind references to null pointers:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285
This is undefined behavior and reported as an error if compiling with `-fsanitize=null`.
### Patches
We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will rel
OSV
CVE-2020-15191: In Tensorflow before versions 2
osv·2020-09-25
CVE-2020-15191 CVE-2020-15191: In Tensorflow before versions 2
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.
GHSA
Undefined behavior in Tensorflow
ghsa·2020-09-25
CVE-2020-15191 [MEDIUM] CWE-20 Undefined behavior in Tensorflow
Undefined behavior in Tensorflow
### Impact
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:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267
Hence, code following these methods will bind references to null pointers:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285
This is undefined behavior and reported as an error if compiling with `-fsanitize=null`.
### Patches
We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will rel
Debian
CVE-2020-15191: tensorflow - In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argum...
vendor_debian·2020·CVSS 5.3
CVE-2020-15191 [MEDIUM] CVE-2020-15191: tensorflow - In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argum...
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.
Scope: local
forky: resolved
sid: resolved
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.htmlhttps://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphrhttp://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.htmlhttps://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr
2020-09-25
Published