4.4
CVSSv3

CVE-2020-26268

Published: 10/12/2020 Updated: 14/12/2020
CVSS v2 Base Score: 3.6 | Impact Score: 4.9 | Exploitability Score: 3.9
CVSS v3 Base Score: 4.4 | Impact Score: 2.5 | Exploitability Score: 1.8
VMScore: 320
Vector: AV:L/AC:L/Au:N/C:N/I:P/A:P

Vulnerability Summary

In affected versions of TensorFlow 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. 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 allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

google tensorflow

Vendor Advisories

In affected versions of TensorFlow the tfraw_opsImmutableConst 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 If the file is too small, TensorFlow prop ...