Denial of service in tensorflow-lite
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-770.
Summary
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation. 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 limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| tensorflow | = 2.2.0; = 2.3.0 | — | No fix listed | CNA | |
| — | tensorflow (PyPI) | 2.2.0 to before 2.2.1 | 2.2.1 | Patch available | GHSA-hjmq-236j-8m87 |
| — | tensorflow (PyPI) | 2.3.0 to before 2.3.1 | 2.3.1 | Patch available | GHSA-hjmq-236j-8m87 |
| — | tensorflow-cpu (PyPI) | 2.2.0 to before 2.2.1 | 2.2.1 | Patch available | GHSA-hjmq-236j-8m87 |
| — | tensorflow-cpu (PyPI) | 2.3.0 to before 2.3.1 | 2.3.1 | Patch available | GHSA-hjmq-236j-8m87 |
| — | tensorflow-gpu (PyPI) | 2.2.0 to before 2.2.1 | 2.2.1 | Patch available | GHSA-hjmq-236j-8m87 |
| — | tensorflow-gpu (PyPI) | 2.3.0 to before 2.3.1 | 2.3.1 | Patch available | GHSA-hjmq-236j-8m87 |
- tensorflow VendorGoogle Affected = 2.2.0; = 2.3.0 Fixed in — No fix listed CNA
- tensorflow (PyPI) Vendor— Affected 2.2.0 to before 2.2.1 Fixed in 2.2.1 Patch available GHSA-hjmq-236j-8m87
- tensorflow (PyPI) Vendor— Affected 2.3.0 to before 2.3.1 Fixed in 2.3.1 Patch available GHSA-hjmq-236j-8m87
- tensorflow-cpu (PyPI) Vendor— Affected 2.2.0 to before 2.2.1 Fixed in 2.2.1 Patch available GHSA-hjmq-236j-8m87
- tensorflow-cpu (PyPI) Vendor— Affected 2.3.0 to before 2.3.1 Fixed in 2.3.1 Patch available GHSA-hjmq-236j-8m87
- tensorflow-gpu (PyPI) Vendor— Affected 2.2.0 to before 2.2.1 Fixed in 2.2.1 Patch available GHSA-hjmq-236j-8m87
- tensorflow-gpu (PyPI) Vendor— Affected 2.3.0 to before 2.3.1 Fixed in 2.3.1 Patch available GHSA-hjmq-236j-8m87
Remediation
- Fix · GHSA-hjmq-236j-8m87 tensorflow (PyPI) Fixed in 2.2.1 Advisory →
- Fix · GHSA-hjmq-236j-8m87 tensorflow (PyPI) Fixed in 2.3.1 Advisory →
- Fix · GHSA-hjmq-236j-8m87 tensorflow-cpu (PyPI) Fixed in 2.2.1 Advisory →
- Fix · GHSA-hjmq-236j-8m87 tensorflow-cpu (PyPI) Fixed in 2.3.1 Advisory →
- Fix · GHSA-hjmq-236j-8m87 tensorflow-gpu (PyPI) Fixed in 2.2.1 Advisory →
- Fix · GHSA-hjmq-236j-8m87 tensorflow-gpu (PyPI) Fixed in 2.3.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2020-15213
- 2026-10-03 Alias added: GHSA-hjmq-236j-8m87
References
Advisory 2
Other 7
- https://github.com/tensorflow/tensorflow/commit/00c7ed7ce81c2126ebc17dfe7073b5c0efd5ec0a
- https://github.com/tensorflow/tensorflow/commit/a4030d8ba3692c438997c27be2dd95f3d5f54827
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-293.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-328.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-136.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44
More Google Tensorflow vulnerabilities
- TI-2022-20241 FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07640 Integer overflow in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07627 Out of bounds read and write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07619 Out of bounds write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07613 Read and Write outside of bounds in TFLite CVSS 3.1HIGH 8.8
- TI-2022-07612 Integer overflow in TFLite CVSS 3.1HIGH 8.8
Sources
- CVE-2020-15213 · CVE Program
- CVE-2020-15213 · NVD
- FIRST EPSS
- GHSA-hjmq-236j-8m87 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences