Loading HuntDB...

CVE-2020-15209

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

Expert Analysis

Professional remediation guidance

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

CVSS Score

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

EPSS Score

v2025.03.14
0.004
probability
of exploitation in the wild

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

Updated: 2025-06-25
Exploit Probability
Percentile: 0.572
Higher than 57.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
NONE
Availability
HIGH

Description

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, 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 HIGH

Null pointer dereference in tensorflow-lite

GHSA-qh32-6jjc-qprm

Advisory Details

### Impact A crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L1224-L1227 However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. ### Patches We have patched the issue in 0b5662bc 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 but was also discovered through 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-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

7.5

CVSS Vector

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

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

References

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