Loading HuntDB...

CVE-2020-15207

HIGH
Published 2020-09-25T18:45:46
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2020-15207. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
8.7
/10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.014
probability
of exploitation in the wild

There is a 1.4% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.796
Higher than 79.6% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED

Impact Metrics

Confidentiality
NONE
Integrity
HIGH
Availability
HIGH

Description

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, 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. 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. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

Segfault and data corruption in tensorflow-lite

GHSA-q4qf-3fc6-8x34

Advisory 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](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) 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.

Affected Packages

PyPI tensorflow
ECOSYSTEM: ≥0 <1.15.4
PyPI tensorflow
ECOSYSTEM: ≥2.0.0 <2.0.3
PyPI tensorflow
ECOSYSTEM: ≥2.1.0 <2.1.2
PyPI tensorflow
ECOSYSTEM: ≥2.2.0 <2.2.1
PyPI tensorflow
ECOSYSTEM: ≥2.3.0 <2.3.1
PyPI tensorflow-cpu
ECOSYSTEM: ≥0 <1.15.4
PyPI tensorflow-cpu
ECOSYSTEM: ≥2.0.0 <2.0.3
PyPI tensorflow-cpu
ECOSYSTEM: ≥2.1.0 <2.1.2
PyPI tensorflow-cpu
ECOSYSTEM: ≥2.2.0 <2.2.1
PyPI tensorflow-cpu
ECOSYSTEM: ≥2.3.0 <2.3.1
PyPI tensorflow-gpu
ECOSYSTEM: ≥0 <1.15.4
PyPI tensorflow-gpu
ECOSYSTEM: ≥2.0.0 <2.0.3
PyPI tensorflow-gpu
ECOSYSTEM: ≥2.1.0 <2.1.2
PyPI tensorflow-gpu
ECOSYSTEM: ≥2.2.0 <2.2.1
PyPI tensorflow-gpu
ECOSYSTEM: ≥2.3.0 <2.3.1

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H

Advisory provided by GitHub Security Advisory Database. Published: September 25, 2020, Modified: October 30, 2024

References

Published: 2020-09-25T18:45:46
Last Modified: 2024-08-04T13:08:22.887Z
Copied to clipboard!