CVE-2020-15212: Out of bounds access in tensorflow-lite
Impact In TensorFlow Lite models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/referenceops.h#L2625-L2631
Users having access to segmentidsdata can alter outputindex and then write to outside of outputdata 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.
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 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.
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 writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to segmentidsdata can alter outputindex and then write to outside of outputdata 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2020-15212?
CVE-2020-15212 is classified as a high severity vulnerability due to the potential for heap buffer overflows.
How do I fix CVE-2020-15212?
To fix CVE-2020-15212, upgrade TensorFlow to version 2.3.1 or later.
Which versions of TensorFlow are affected by CVE-2020-15212?
CVE-2020-15212 affects TensorFlow versions 2.2.0 to 2.2.1 and 2.3.0.
What impact does CVE-2020-15212 have on TensorFlow Lite models?
CVE-2020-15212 can trigger writes outside of bounds in TensorFlow Lite models when using segment sum with negative segment IDs.
Is CVE-2020-15212 a local or remote execution vulnerability?
CVE-2020-15212 is primarily a local execution vulnerability affecting applications using TensorFlow Lite.