Advisory
GHSA-qhxx-j73r-qpm2
Also known as: BIT-tensorflow-2020-26266, CVE-2020-26266, PYSEC-2020-254, PYSEC-2020-297, PYSEC-2020-332
Summary
Uninitialized memory access in TensorFlow
Details
Impact
Under certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen:
struct QUInt8 {
QUInt8() {}
// ...
uint8_t value;
};
struct QInt16 {
QInt16() {}
// ...
int16_t value;
};
struct QUInt16 {
QUInt16() {}
// ...
uint16_t value;
};
struct QInt32 {
QInt32() {}
// ...
int32_t value;
};
Patches
We have patched the issue in GitHub commit ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Severity
Medium Basis: The source's own band: MODERATE
Dates
- Published
- 2020-12-10 19:07 UTC
- Modified
- 2026-07-08 06:00 UTC
Affected packages and fixes
| Package | Affected | Fix |
|---|---|---|
| tensorflow | Earlier versions | pip install --upgrade tensorflow==1.15.5 |
| tensorflow | introduced 2.0.0, fixed 2.0.4 | pip install --upgrade tensorflow==2.0.4 |
| tensorflow | introduced 2.1.0, fixed 2.1.3 | pip install --upgrade tensorflow==2.1.3 |
| tensorflow | introduced 2.2.0, fixed 2.2.2 | pip install --upgrade tensorflow==2.2.2 |
| tensorflow | introduced 2.3.0, fixed 2.3.2 | pip install --upgrade tensorflow==2.3.2 |
| tensorflow-cpu | Earlier versions | pip install --upgrade tensorflow-cpu==1.15.5 |
| tensorflow-cpu | introduced 2.0.0, fixed 2.0.4 | pip install --upgrade tensorflow-cpu==2.0.4 |
| tensorflow-cpu | introduced 2.1.0, fixed 2.1.3 | pip install --upgrade tensorflow-cpu==2.1.3 |
| tensorflow-cpu | introduced 2.2.0, fixed 2.2.2 | pip install --upgrade tensorflow-cpu==2.2.2 |
| tensorflow-cpu | introduced 2.3.0, fixed 2.3.2 | pip install --upgrade tensorflow-cpu==2.3.2 |
| tensorflow-gpu | Earlier versions | pip install --upgrade tensorflow-gpu==1.15.5 |
| tensorflow-gpu | introduced 2.0.0, fixed 2.0.4 | pip install --upgrade tensorflow-gpu==2.0.4 |
| tensorflow-gpu | introduced 2.1.0, fixed 2.1.3 | pip install --upgrade tensorflow-gpu==2.1.3 |
| tensorflow-gpu | introduced 2.2.0, fixed 2.2.2 | pip install --upgrade tensorflow-gpu==2.2.2 |
| tensorflow-gpu | introduced 2.3.0, fixed 2.3.2 | pip install --upgrade tensorflow-gpu==2.3.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-qhxx-j73r-qpm2
- https://nvd.nist.gov/vuln/detail/CVE-2020-26266
- https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-297.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-332.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-254.yaml
- https://github.com/tensorflow/tensorflow
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0