Advisory
GHSA-q4qf-3fc6-8x34
Also known as: BIT-tensorflow-2020-15207, CVE-2020-15207, PYSEC-2020-130, PYSEC-2020-287, PYSEC-2020-322
Summary
Segfault and data corruption in tensorflow-lite
Details
Impact
To mimic Python's indexing with negative values, TFLite uses ResolveAxis to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reduce.h#L68-L72
If the DCHECK does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption.
Patches
We have patched the issue in 2d88f470dea2671b430884260f3626b1fe99830a and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
Severity
Medium Basis: The source's own band: MODERATE
Dates
- Published
- 2020-09-25 18:28 UTC
- Modified
- 2026-09-10 03:48 UTC
Affected packages and fixes
| Package | Affected | Fix |
|---|---|---|
| tensorflow | Earlier versions | pip install --upgrade tensorflow==1.15.4 |
| tensorflow | introduced 2.0.0, fixed 2.0.3 | pip install --upgrade tensorflow==2.0.3 |
| tensorflow | introduced 2.1.0, fixed 2.1.2 | pip install --upgrade tensorflow==2.1.2 |
| tensorflow | introduced 2.2.0, fixed 2.2.1 | pip install --upgrade tensorflow==2.2.1 |
| tensorflow | introduced 2.3.0, fixed 2.3.1 | pip install --upgrade tensorflow==2.3.1 |
| tensorflow-cpu | Earlier versions | pip install --upgrade tensorflow-cpu==1.15.4 |
| tensorflow-cpu | introduced 2.0.0, fixed 2.0.3 | pip install --upgrade tensorflow-cpu==2.0.3 |
| tensorflow-cpu | introduced 2.1.0, fixed 2.1.2 | pip install --upgrade tensorflow-cpu==2.1.2 |
| tensorflow-cpu | introduced 2.2.0, fixed 2.2.1 | pip install --upgrade tensorflow-cpu==2.2.1 |
| tensorflow-cpu | introduced 2.3.0, fixed 2.3.1 | pip install --upgrade tensorflow-cpu==2.3.1 |
| tensorflow-gpu | Earlier versions | pip install --upgrade tensorflow-gpu==1.15.4 |
| tensorflow-gpu | introduced 2.0.0, fixed 2.0.3 | pip install --upgrade tensorflow-gpu==2.0.3 |
| tensorflow-gpu | introduced 2.1.0, fixed 2.1.2 | pip install --upgrade tensorflow-gpu==2.1.2 |
| tensorflow-gpu | introduced 2.2.0, fixed 2.2.1 | pip install --upgrade tensorflow-gpu==2.2.1 |
| tensorflow-gpu | introduced 2.3.0, fixed 2.3.1 | pip install --upgrade tensorflow-gpu==2.3.1 |
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Links
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34
- https://nvd.nist.gov/vuln/detail/CVE-2020-15207
- https://github.com/tensorflow/tensorflow/commit/2d88f470dea2671b430884260f3626b1fe99830a
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-287.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-322.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-130.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0