CVE-2020-15214
Out of bounds write in tensorflow-lite
- Published
- Updated
- Reserved
- Assigned by
- GitHub_M
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.
Timeline
ID reserved
By GitHub_M
- 3 months later
· 3 months later
Published
- 4 years later
· 4 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H |
| NVDNVD · Modified | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.67% · top 48% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Weakness
Affected products
- affected >= 2.2.0, < 2.2.1
- affected >= 2.3.0, < 2.3.1
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- PyPItensorflowGHSA-p2cq-cprg-frvm (opens in a new tab)
- PyPItensorflow-cpuGHSA-p2cq-cprg-frvm (opens in a new tab)
- PyPItensorflow-gpuGHSA-p2cq-cprg-frvm (opens in a new tab)
References (3)
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a (opens in a new tab)x_refsource_MISCx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-p2cq-cprg-frvm (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2020-15214)Record last updated .