Advisory
GHSA-jf7h-7m85-w2v2
Also known as: BIT-tensorflow-2021-29605, CVE-2021-29605, PYSEC-2021-242, PYSEC-2021-533, PYSEC-2021-731
Summary
Integer overflow in TFLite memory allocation
Details
Impact
The TFLite code for allocating TFLiteIntArrays is vulnerable to an integer overflow issue:
int TfLiteIntArrayGetSizeInBytes(int size) {
static TfLiteIntArray dummy;
return sizeof(dummy) + sizeof(dummy.data[0]) * size;
}
An attacker can craft a model such that the size multiplier is so large that the return value overflows the int datatype and becomes negative. In turn, this results in invalid value being given to `malloc`:
TfLiteIntArray* TfLiteIntArrayCreate(int size) {
TfLiteIntArray* ret = (TfLiteIntArray*)malloc(TfLiteIntArrayGetSizeInBytes(size));
ret->size = size;
return ret;
}
In this case, ret->size would dereference an invalid pointer.
Patches
We have patched the issue in GitHub commit 7c8cc4ec69cd348e44ad6a2699057ca88faad3e5.
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
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.
Severity
Medium Basis: The source's own band: MODERATE
Dates
- Published
- 2021-05-21 14:28 UTC
- Modified
- 2026-09-10 03:49 UTC
Affected packages and fixes
| Package | Affected | Fix |
|---|---|---|
| tensorflow | Earlier versions | pip install --upgrade tensorflow==2.1.4 |
| tensorflow | introduced 2.2.0, fixed 2.2.3 | pip install --upgrade tensorflow==2.2.3 |
| tensorflow | introduced 2.3.0, fixed 2.3.3 | pip install --upgrade tensorflow==2.3.3 |
| tensorflow | introduced 2.4.0, fixed 2.4.2 | pip install --upgrade tensorflow==2.4.2 |
| tensorflow-cpu | Earlier versions | pip install --upgrade tensorflow-cpu==2.1.4 |
| tensorflow-cpu | introduced 2.2.0, fixed 2.2.3 | pip install --upgrade tensorflow-cpu==2.2.3 |
| tensorflow-cpu | introduced 2.3.0, fixed 2.3.3 | pip install --upgrade tensorflow-cpu==2.3.3 |
| tensorflow-cpu | introduced 2.4.0, fixed 2.4.2 | pip install --upgrade tensorflow-cpu==2.4.2 |
| tensorflow-gpu | Earlier versions | pip install --upgrade tensorflow-gpu==2.1.4 |
| tensorflow-gpu | introduced 2.2.0, fixed 2.2.3 | pip install --upgrade tensorflow-gpu==2.2.3 |
| tensorflow-gpu | introduced 2.3.0, fixed 2.3.3 | pip install --upgrade tensorflow-gpu==2.3.3 |
| tensorflow-gpu | introduced 2.4.0, fixed 2.4.2 | pip install --upgrade tensorflow-gpu==2.4.2 |
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Links
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jf7h-7m85-w2v2
- https://nvd.nist.gov/vuln/detail/CVE-2021-29605
- https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-533.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-731.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-242.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L24-L27
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0