Critical

Out of bounds write in tensorflow-lite

  • Disclosed: 25.09.2020
  • Updated: 11.10.2026 13:19

Impact

In TensorFlow Lite 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: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44

This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631

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.

Patches

We have patched the issue in 204945b and will release patch releases for all affected versions.

We recommend users to upgrade to TensorFlow 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 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.

For more information

Please consult our security guide 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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) tensorflow >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 2.2.1, 2.3.1
Python (PyPI) tensorflow-cpu >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 2.2.1, 2.3.1
Python (PyPI) tensorflow-gpu >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 2.2.1, 2.3.1

References

CVSS score 8.1/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
Weakness (CWE)
CWE-787
Platform
Python (PyPI)
Package
tensorflow, tensorflow-cpu, tensorflow-gpu
Disclosed
25.09.2020
Updated
11.10.2026 13:19

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2020-137 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2020-294 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2020-329 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-p2cq-cprg-frvm - CC BY 4.0

Vulnerability history: tensorflow

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (433) in the archive
Total entries
433
First → latest
04.2019 07.2024
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 112
  • Medium 210
  • Low 105

Disclosures per year

  1. 2019: 7
  2. 2020: 35
  3. 2021: 200
  4. 2022: 169
  5. 2023: 21
  6. 2024: 1
  7. 2025: 0
  8. 2026: 0
Severity:
  1. Out of bounds write in tensorflow-lite this entry
    Critical · 8.1 CVE-2020-15214 >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 2.2.1, 2.3.1
  2. High · 7.5 CVE-2023-33976 < 2.12.1 2.12.1
  3. High · 7.5 CVE-2023-25659 < 2.11.1 2.11.1
  4. High · 7.5 CVE-2023-25660 < 2.11.1 2.11.1
  5. High · 7.5 CVE-2023-25662 < 2.11.1 2.11.1
  6. High · 7.5 CVE-2023-25663 < 2.11.1 2.11.1
  7. High · 7.5 CVE-2023-25664 < 2.11.1 2.11.1
  8. High · 7.5 CVE-2023-25665 < 2.11.1 2.11.1
  9. High · 7.5 CVE-2023-25666 < 2.11.1 2.11.1
  10. High · 7.5 CVE-2023-25669 < 2.11.1 2.11.1
  11. High · 7.5 CVE-2023-25671 < 2.11.1 2.11.1
  12. High · 7.5 CVE-2023-25672 < 2.11.1 2.11.1
  13. High · 7.5 CVE-2023-25673 < 2.11.1 2.11.1
  14. High · 7.5 CVE-2023-25674 < 2.11.1 2.11.1
  15. High · 7.5 CVE-2023-25675 < 2.11.1 2.11.1
  16. High · 7.5 CVE-2023-25676 < 2.11.1 2.11.1
  17. High · 8.0 CVE-2023-25801 < 2.11.1 2.11.1
  18. High · 7.5 CVE-2023-27579 < 2.11.1 2.11.1
  19. High · 7.5 CVE-2023-25658 < 2.11.1 2.11.1
Show more (20) Showing 21 of 118

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.