p PatchFirst

PatchFirst · Latest vulnerabilities

tensorflow-cpu vulnerabilities · Page 22

Vulnerabilities published for tensorflow-cpu in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗ JSON ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 430

  1. CVE-2020-15190

    Medium · CVSS 5.3EPSS 0.94%Fix available

    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 other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da85

    tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Update to 1.15.4
    • Update to 2.0.3
    • Update to 2.1.2
    • Update to 2.2.1
    • Update to 2.3.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  3. CVE-2020-5215

    Medium · CVSS 5EPSS 0.59%Fix available

    Segmentation faultin TensorFlow when converting a Python string to tf.float16

    In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant("hello", tf.float16), if eager exe

    tensorflow-cpu tensorflow-cpu tensorflow-cpuPython
    • Update to 1.15.2
    • Update to 2.0.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  4. CVE-2019-16778

    Low · CVSS 2.6EPSS 0.79%Fix available

    Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow

    In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.

    tensorflow-cpu tensorflow-cpuPython
    • Update to 1.15.0
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  7. CVE-2018-10055

    High · CVSS 8.1EPSS 0.53%Fix available

    CVE-2018-10055

    Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file.

    tensorflow-cpuPython
    • Update to 1.7.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →