Skip to content
Fencer Vulns
high 8.1

CVE-2020-15212 json

Out of bounds access in tensorflow-lite

published 2020-09-25 6 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2020-15212 , EUVD-2020-0208 , GHSA-hx2x-85gr-wrpq , PYSEC-2020-135 , PYSEC-2020-292 , PYSEC-2020-327

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced 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 all positive, 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.

Patch / fix

  • pypi tensorflow 2.2.1, 2.3.1
  • pypi tensorflow-cpu 2.2.1, 2.3.1
  • pypi tensorflow-gpu 2.2.1, 2.3.1
  • bitnami tensorflow 2.2.1, 2.3.1
  • google tensorflow 2.2.1, 2.3.1

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hx2x-85gr-wrpq referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
>=2.2.0, <2.2.1
>=2.3.0, <2.3.1
2.2.1
2.3.1
pypi tensorflow-cpu
>=2.2.0, <2.2.1
>=2.3.0, <2.3.1
2.2.1
2.3.1
pypi tensorflow-gpu
>=2.2.0, <2.2.1
>=2.3.0, <2.3.1
2.2.1
2.3.1
bitnami tensorflow
>=2.2.0, <2.2.1
>=2.3.0, <2.3.1
2.2.1
2.3.1

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.