Advisory
GHSA-hhvc-g5hv-48c6
Also known as: BIT-tensorflow-2020-26268, CVE-2020-26268, PYSEC-2020-255, PYSEC-2020-299, PYSEC-2020-334
Summary
Write to immutable memory region in TensorFlow
Details
Impact
The tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area:
>>> import tensorflow as tf
>>> with open('/tmp/test.txt','w') as f: f.write('a'*128)
>>> tf.raw_ops.ImmutableConst(dtype=tf.string,shape=2,
memory_region_name='/tmp/test.txt')
If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault.
This is because the alocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overriden.
Patches
We have patched the issue in GitHub commit c1e1fc899ad5f8c725dcbb6470069890b5060bc7 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.
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
- 2020-12-10 19:07 UTC
- Modified
- 2026-09-10 03:48 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-hhvc-g5hv-48c6
- https://nvd.nist.gov/vuln/detail/CVE-2020-26268
- https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-299.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-334.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-255.yaml
- https://github.com/tensorflow/tensorflow
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0