Summary
This update for tensorflow2 fixes the following issues:
- updated to 2.1.2 with following fixes (boo#1177022):
* Fixes an undefined behavior causing a segfault in tf.raw_ops.Switch (CVE-2020-15190)
* Fixes three vulnerabilities in conversion to DLPack format (CVE-2020-15191, CVE-2020-15192, CVE-2020-15193)
* Fixes two vulnerabilities in SparseFillEmptyRowsGrad (CVE-2020-15194, CVE-2020-15195)
* Fixes an integer truncation vulnerability in code using the work sharder API (CVE-2020-15202)
* Fixes a format string vulnerability in tf.strings.as_string (CVE-2020-15203)
* Fixes segfault raised by calling session-only ops in eager mode (CVE-2020-15204)
* Fixes data leak and potential ASLR violation from tf.raw_ops.StringNGrams (CVE-2020-15205)
* Fixes segfaults caused by incomplete SavedModel validation (CVE-2020-15206)
* Fixes a data corruption due to a bug in negative indexing support in TFLite (CVE-2020-15207)
* Fixes a data corruption due to dimension mismatch in TFLite (CVE-2020-15208)
* Fixes several vulnerabilities in TFLite saved model format (CVE-2020-15209, CVE-2020-15210, CVE-2020-15211)
Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.2 | tensorflow2 | 2.1.2-lp152.7.3.1 |
| openSUSE · Leap 15.2 | tensorflow2_2_1_2-gnu-hpc | 2.1.2-lp152.7.3.1 |
| openSUSE · Leap 15.2 | tensorflow2_2_1_2-gnu-openmpi2-hpc | 2.1.2-lp152.7.3.1 |
| openSUSE · Leap 15.2 | tensorflow2-lite | 2.1.2-lp152.7.3.1 |
Vulnerabilities 16
-
Critical 9.0
Integer truncation in Shard API usage
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taki…
-
Critical 9.0
Data leak in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked…
-
Critical 9.0
Denial of Service in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of ser…
-
High 8.7
Segfault and data corruption in tensorflow-lite
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid …
-
High 8.5
Heap buffer overflow in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of `SparseFillEmptyRowsGrad` uses a double indexing pattern. It is possible for `reverse_index_map(i)` to be an index outside of bounds of `grad_values`, thus resulting in…
-
High 7.5
Denial of Service in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is…
-
High 7.4
Data corruption in tensorflow-lite
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of t…
-
High 7.1
Memory corruption in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, ther…
-
Medium 6.5
Segmentation fault in tensorflow-lite
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We …
-
Medium 5.9
Null pointer dereference in tensorflow-lite
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to conver…
-
Medium 5.3
Segfault in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the ot…
-
Medium 5.3
Undefined behavior in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argum…
-
Medium 5.3
Denial of Service in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, o…
-
Medium 5.3
Segfault in Tensorflow
In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference In linked snippet, in eager m…
-
Medium 4.8
Out of bounds access in tensorflow-lite
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tens…
-
Medium 4.3
Memory leak in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure. The issue occurs because the `status` argument during validation failures is not properly …
References
-
report
https://bugzilla.suse.com/1173314
-
report
https://bugzilla.suse.com/1175099
-
report
https://bugzilla.suse.com/1175789
-
report
https://bugzilla.suse.com/1177022
-
web
https://www.suse.com/security/cve/CVE-2020-15190
-
web
https://www.suse.com/security/cve/CVE-2020-15191
-
web
https://www.suse.com/security/cve/CVE-2020-15192
-
web
https://www.suse.com/security/cve/CVE-2020-15193
-
web
https://www.suse.com/security/cve/CVE-2020-15194
-
web
https://www.suse.com/security/cve/CVE-2020-15195
-
web
https://www.suse.com/security/cve/CVE-2020-15202
-
web
https://www.suse.com/security/cve/CVE-2020-15203
-
web
https://www.suse.com/security/cve/CVE-2020-15204
-
web
https://www.suse.com/security/cve/CVE-2020-15205
-
web
https://www.suse.com/security/cve/CVE-2020-15206
-
web
https://www.suse.com/security/cve/CVE-2020-15207
-
web
https://www.suse.com/security/cve/CVE-2020-15208
-
web
https://www.suse.com/security/cve/CVE-2020-15209
-
web
https://www.suse.com/security/cve/CVE-2020-15210
-
web
https://www.suse.com/security/cve/CVE-2020-15211