CVE-2020-15213: Denial of service in tensorflow-lite
Impact In TensorFlow Lite 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: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segmentsum.cc#L39-L44
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 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.
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 discovered from a variant analysis of GHSA-p2cq-cprg-frvm.
Other sources
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2020-15213?
CVE-2020-15213 has a severity that can lead to a denial of service due to out of memory errors in TensorFlow Lite models.
How do I fix CVE-2020-15213?
To fix CVE-2020-15213, upgrade to TensorFlow version 2.3.1 or later.
What versions of TensorFlow are affected by CVE-2020-15213?
CVE-2020-15213 affects TensorFlow versions 2.2.0 and 2.3.0.
What is the impact of CVE-2020-15213 on TensorFlow Lite?
The impact of CVE-2020-15213 on TensorFlow Lite is the potential for denial of service due to excessive memory allocation.
Is CVE-2020-15213 related to TensorFlow GPU or CPU packages?
Yes, CVE-2020-15213 is related to both TensorFlow GPU and CPU packages as they both include the vulnerable versions.