p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in tensorflow-cpu · Seite 20

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für tensorflow-cpu: 0. Davon im KEV-Katalog: 0.

RSS ↗ JSON ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 430

  1. CVE-2021-29548

    Niedrig · CVSS 2.5EPSS 0,19%Korrektur verfügbar

    Division by 0 in `QuantizedBatchNormWithGlobalNormalization`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract(https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, Ten

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.4.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  2. CVE-2021-29549

    Niedrig · CVSS 2.5EPSS 0,19%Korrektur verfügbar

    Division by 0 in `QuantizedAdd`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.0rc0 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.0rc0 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.3.4 aktualisieren
    • Auf 2.4.2 aktualisieren
    • Auf 2.4.3 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  3. CVE-2021-29550

    Niedrig · CVSS 2.5EPSS 0,19%Korrektur verfügbar

    Division by 0 in `FractionalAvgPool`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor o

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.0rc0 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.0rc0 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.3.4 aktualisieren
    • Auf 2.4.2 aktualisieren
    • Auf 2.4.3 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  4. CVE-2021-29551

    Niedrig · CVSS 2.5EPSS 0,22%Korrektur verfügbar

    OOB read in `MatrixTriangularSolve`

    TensorFlow is an end-to-end open source platform for machine learning. The implementation of `MatrixTriangularSolve`(https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.0rc0 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.0rc0 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.3.4 aktualisieren
    • Auf 2.4.2 aktualisieren
    • Auf 2.4.3 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  5. CVE-2021-29552

    Niedrig · CVSS 2.5EPSS 0,19%Korrektur verfügbar

    CHECK-failure in `UnsortedSegmentJoin`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar<T>()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination. The fix will be include

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.0rc0 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.0rc0 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.3.4 aktualisieren
    • Auf 2.4.2 aktualisieren
    • Auf 2.4.3 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  6. CVE-2021-29553

    Niedrig · CVSS 2.5EPSS 0,2%Korrektur verfügbar

    Heap OOB in `QuantizeAndDequantizeV3`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can read data outside of bounds of heap allocated buffer in `tf.raw_ops.QuantizeAndDequantizeV3`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/11ff7f80667e6490d7b5174aa6bf5e01886e770f/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L237) does not validate the value of user supplied `axis` attribute before using it to index in the array backing the `input` argument. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.4.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  7. CVE-2021-29554

    Niedrig · CVSS 2.5EPSS 0,19%Korrektur verfügbar

    Division by 0 in `DenseCountSparseOutput`

    TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division. Since `data` is given by the `values` argument, `num_batch_elements` is 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.1.4 aktualisieren
    • Auf 2.2.3 aktualisieren
    • Auf 2.3.3 aktualisieren
    • Auf 2.4.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  8. CVE-2021-29512

    Niedrig · CVSS 2.5EPSS 0,21%Korrektur verfügbar

    Heap buffer overflow in `RaggedBinCount`

    TensorFlow is an end-to-end open source platform for machine learning. If the `splits` argument of `RaggedBincount` does not specify a valid `SparseTensor`(https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the `splits` tensor buffer in the implementation of the `RaggedBincount` op(https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.3.3 aktualisieren
    • Auf 2.4.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  9. CVE-2020-26266

    Mittel · CVSS 4.4EPSS 0,26%Korrektur verfügbar

    Uninitialized memory access in Eigen types in TensorFlow

    In affected versions of TensorFlow 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. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 1.15.5 aktualisieren
    • Auf 2.0.4 aktualisieren
    • Auf 2.1.3 aktualisieren
    • Auf 2.2.2 aktualisieren
    • Auf 2.3.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  10. CVE-2020-26267

    Mittel · CVSS 4.4EPSS 0,24%Korrektur verfügbar

    Lack of validation in data format attributes in TensorFlow

    In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 1.15.5 aktualisieren
    • Auf 2.0.4 aktualisieren
    • Auf 2.1.3 aktualisieren
    • Auf 2.2.2 aktualisieren
    • Auf 2.3.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  11. CVE-2020-26268

    Mittel · CVSS 4.4EPSS 0,21%Korrektur verfügbar

    Write to immutable memory region in TensorFlow

    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

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 1.15.5 aktualisieren
    • Auf 2.0.4 aktualisieren
    • Auf 2.1.3 aktualisieren
    • Auf 2.2.2 aktualisieren
    • Auf 2.3.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  12. CVE-2020-26269

    Kritisch · CVSS 9.1EPSS 0,7%Korrektur verfügbar

    Heap out of bounds read in filesystem glob matching in TensorFlow

    In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patch

    tensorflow-cpu tensorflow-cpuPython
    • Auf 2.4.0 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  13. CVE-2020-26270

    Mittel · CVSS 4.4EPSS 0,17%Korrektur verfügbar

    CHECK-fail in LSTM with zero-length input in TensorFlow

    In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 1.15.5 aktualisieren
    • Auf 2.0.4 aktualisieren
    • Auf 2.1.3 aktualisieren
    • Auf 2.2.2 aktualisieren
    • Auf 2.3.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  14. CVE-2020-26271

    Mittel · CVSS 4.4EPSS 0,22%Korrektur verfügbar

    Heap out of bounds access in MakeEdge in TensorFlow

    In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 1.15.5 aktualisieren
    • Auf 2.0.4 aktualisieren
    • Auf 2.1.3 aktualisieren
    • Auf 2.2.2 aktualisieren
    • Auf 2.3.2 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  15. CVE-2020-15266

    Niedrig · CVSS 3.7EPSS 0,94%Korrektur verfügbar

    Undefined behavior in Tensorflow

    In Tensorflow before version 2.4.0, when the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.

    tensorflow-cpuPython
    • Auf 2.4.0 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  16. CVE-2020-15265

    Mittel · CVSS 5.9EPSS 0,91%Korrektur verfügbar

    Segfault in Tensorflow

    In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this c

    tensorflow-cpu tensorflow-cpuPython
    • Auf 2.4.0 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  17. CVE-2020-15212

    Hoch · CVSS 8.1EPSS 0,74%Korrektur verfügbar

    Out of bounds access in tensorflow-lite

    In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would b

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.2.1 aktualisieren
    • Auf 2.3.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  18. CVE-2020-15213

    Mittel · CVSS 4EPSS 0,76%Korrektur verfügbar

    Denial of service in tensorflow-lite

    In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to limit the maximum value in the segment ids tensor. This only handles the case when the segment i

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.2.1 aktualisieren
    • Auf 2.3.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  19. CVE-2020-15214

    Hoch · CVSS 8.1EPSS 0,67%Korrektur verfügbar

    Out of bounds write in tensorflow-lite

    In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 2

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Auf 2.2.1 aktualisieren
    • Auf 2.3.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  20. CVE-2020-15201

    Mittel · CVSS 4.8EPSS 0,57%Korrektur verfügbar

    Heap buffer overflow in Tensorflow

    In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, the code is prone to heap buffer overflow. If `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

    tensorflow-cpu tensorflow-cpuPython
    • Auf 2.3.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →