CVE-2020-15191 json
Undefined behavior in Tensorflow
published 6y ago modified 2mo ago also BIT-tensorflow-2020-15191 , EUVD-2020-0187 , GHSA-q8qj-fc9q-cphr , PYSEC-2020-114 , PYSEC-2020-271 , PYSEC-2020-306
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi tensorflow 2.2.1, 2.3.1
- pypi tensorflow-cpu 2.2.1, 2.3.1
- pypi tensorflow-gpu 2.2.1, 2.3.1
- bitnami tensorflow 2.2.1, 2.3.1
- tensorflow2 openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2-lite openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2_2_1_2-gnu-hpc openSUSE Leap 15.2 2.1.2-lp152.7.3.1
- tensorflow2_2_1_2-gnu-openmpi2-hpc openSUSE Leap 15.2 2.1.2-lp152.7.3.1
opensuse advisories openSUSE-SU-2020:1766-1
Is CVE-2020-15191 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | >=2.2.0, <2.2.1 >=2.3.0, <2.3.1 <2.2.1 >=2.3.0rc0, <2.3.1 |
2.2.1 2.3.1 |
| pypi | tensorflow-cpu | >=2.2.0, <2.2.1 >=2.3.0, <2.3.1 <2.2.1 >=2.3.0rc0, <2.3.1 |
2.2.1 2.3.1 |
| pypi | tensorflow-gpu | >=2.2.0, <2.2.1 >=2.3.0, <2.3.1 <2.2.1 >=2.3.0rc0, <2.3.1 |
2.2.1 2.3.1 |
| bitnami | tensorflow | >=2.2.0, <2.2.1 >=2.3.0, <2.3.1 |
2.2.1 2.3.1 |
Affected products
- tensorflow tensorflow
Classification
References
-
github.com
/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-q8qj-fc9q-cphr
web, exploit, third-party-advisory, advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-10/msg00065.html
vendor-advisory, web, mailing-list, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.3.1
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15191
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-271.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-306.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-114.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2020-15191
- GitHub Advisory GHSA-q8qj-fc9q-cphr
- NVD CVE-2020-15191
- OSV BIT-tensorflow-2020-15191
- OSV PYSEC-2020-114
- OSV PYSEC-2020-271
- OSV PYSEC-2020-306
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.