CVE-2020-15214— Out of bounds write in tensorflow-lite
Quick assessment
Affected
tensorflow tensorflow
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Google TensorFlow是美国谷歌（Google）公司的一套用于机器学习的端到端开源平台。 TensorFlow Lite 2.2.1之前版本，2.3.1版本中存在安全漏洞，该漏洞允许攻击者进行越界内存操作，导致内存泄漏问题。
Possible ATT&CK Techniques 1 AI
T1203 · Exploitation for Client Execution
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2020-15214
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Out of bounds write in tensorflow-lite
Source: CVE Program / CVE List V5
Vulnerability Description
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
跨界内存写
Source: CVE Program / CVE List V5
Vulnerability Title
Google TensorFlow 缓冲区错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Google TensorFlow是美国谷歌（Google）公司的一套用于机器学习的端到端开源平台。 TensorFlow Lite 2.2.1之前版本，2.3.1版本中存在安全漏洞，该漏洞允许攻击者进行越界内存操作，导致内存泄漏问题。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| tensorflow | tensorflow | >= 2.2.0, < 2.2.1 | - |
|
II. Public POCs for CVE-2020-15214
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2020-15214
请登录查看更多情报信息。
Patches & Fixes for CVE-2020-15214 (1)
Vendor Advisories for CVE-2020-15214 (1)
-
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm x_refsource_CONFIRM
Other References for CVE-2020-15214 (1)
-
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 x_refsource_MISC
Same Patch Batch · tensorflow · 2020-09-25 · 25 CVEs total
| CVE-2020-15202 | 9.0 CRITICAL | Integer truncation in Shard API usage |
| CVE-2020-15205 | 9.0 CRITICAL | Data leak in Tensorflow |
| CVE-2020-15206 | 9.0 CRITICAL | Denial of Service in Tensorflow |
| CVE-2020-15207 | 8.7 HIGH | Segfault and data corruption in tensorflow-lite |
| CVE-2020-15196 | 8.5 HIGH | Heap buffer overflow in Tensorflow |
| CVE-2020-15195 | 8.5 HIGH | Heap buffer overflow in Tensorflow |
| CVE-2020-15212 | 8.1 HIGH | Out of bounds access in tensorflow-lite |
| CVE-2020-15203 | 7.5 HIGH | Denial of Service in Tensorflow |
| CVE-2020-15208 | 7.4 HIGH | Data corruption in tensorflow-lite |
| CVE-2020-15193 | 7.1 HIGH | Memory corruption in Tensorflow |
| CVE-2020-15210 | 6.5 MEDIUM | Segmentation fault in tensorflow-lite |
| CVE-2020-15197 | 6.3 MEDIUM | Denial of Service in Tensorflow |
| CVE-2020-15209 | 5.9 MEDIUM | Null pointer dereference in tensorflow-lite |
| CVE-2020-15199 | 5.9 MEDIUM | Denial of Service in Tensorflow |
| CVE-2020-15200 | 5.9 MEDIUM | Segfault in Tensorflow |
| CVE-2020-15198 | 5.4 MEDIUM | Heap buffer overflow in Tensorflow |
| CVE-2020-15190 | 5.3 MEDIUM | Segfault in Tensorflow |
| CVE-2020-15191 | 5.3 MEDIUM | Undefined behavior in Tensorflow |
| CVE-2020-15194 | 5.3 MEDIUM | Denial of Service in Tensorflow |
| CVE-2020-15204 | 5.3 MEDIUM | Segfault in Tensorflow |
Showing top 20 of 25 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: tensorflow
Same vendor: tensorflow
-
CVE-2026-2492
TensorFlow HDF5 Library Uncontrolled Search Path Element Loc -
CVE-2023-33976
TensorFlow segfault in array_ops.upper_bound -
CVE-2024-3660
Arbitrary code injection vulnerability in Keras framework < -
CVE-2023-25661
Denial of Service in TensorFlow -
CVE-2023-25660
TensorFlow vulnerable to seg fault in `tf.raw_ops.Print`
Same weakness: CWE-787
-
CVE-2026-103628
Chrome<154.0.8037.97 WebGL越界写入漏洞 -
CVE-2026-102514
Out-of-bounds write in PeaZip PEA extractor allows code exec -
CVE-2026-103484
pgvector buffer overflow in IVFFlat index build -
CVE-2026-59685
Apache HTTP Server: Out-of-Bounds Write in ap_directory_walk -
CVE-2026-56449
Apache HTTP Server: mod_proxy_html: crash in dump_content
V. Comments for CVE-2020-15214
No comments yet