CVE-2020-15213 Details
Description
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a | CVE | PatchThird Party Advisory |
| https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | CVE | Third Party Advisory |
| https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87 | CVE | ExploitThird Party Advisory |
| https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a | [email protected] | PatchThird Party Advisory |
| https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | [email protected] | Third Party Advisory |
| https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87 | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
| CWE-119 | Improper Restriction of Operations within the Bounds of a Memory Buffer | [email protected] |
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| google tensorflow | >= 2.2.0, < 2.2.1 >= 2.3.0, < 2.3.1 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Nov 18, 2021 | Reanalysis | [email protected] |
| Aug 17, 2021 | CPE Deprecation Remap | [email protected] |
| Aug 17, 2021 | CPE Deprecation Remap | [email protected] |
| Oct 1, 2020 | Initial Analysis | [email protected] |