Denial of Service (DoS) Affecting tensorflow/tensorflow package, versions [,1.15.5)[2.0.0,2.0.4)[2.1.0,2.1.3)[2.2.0,2.2.2)[2.3.0,2.3.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Denial of Service (DoS) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-TENSORFLOWTENSORFLOW-2333345
- published12 Jan 2022
- disclosed10 Dec 2020
- creditUnknown
Introduced: 10 Dec 2020
CVE-2020-26268 (opens in a new tab)How to fix?
Upgrade tensorflow/tensorflow to version 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 or higher.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS). 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.