Loading HuntDB...

CVE-2020-15210

MEDIUM
Published 2020-09-25T18:45:30
Actions:

Expert Analysis

Professional remediation guidance

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

CVSS Score

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

EPSS Score

v2025.03.14
0.003
probability
of exploitation in the wild

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

Updated: 2025-06-25
Exploit Probability
Percentile: 0.552
Higher than 55.2% of all CVEs

Attack Vector Metrics

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

Impact Metrics

Confidentiality
NONE
Integrity
LOW
Availability
HIGH

Description

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b 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.

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 HIGH

Segmentation fault in tensorflow-lite

GHSA-x9j7-x98r-r4w2

Advisory Details

### Impact If a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. ### Patches We have patched the issue in d58c96946b 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. ### Workarounds A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that no operator reuses tensors as both inputs and outputs. Care should be taken to check all types of inputs (i.e., constant or variable tensors as well as optional tensors). ### 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 discovered from a variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).

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-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-cpu
ECOSYSTEM: ≥2.3.0 <2.3.1
PyPI tensorflow-gpu
ECOSYSTEM: ≥2.3.0 <2.3.1

CVSS Scoring

CVSS Score

7.5

CVSS Vector

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

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

References

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