CVE-2020-15190

描述

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 da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

如何修補 CVE-2020-15190

要修補 CVE-2020-15190,請將受影響套件升級到下列已修補版本。

• —升級至 1.15.4 或更新版本
• —升級至 1.15.4 或更新版本
• —升級至 1.15.4 或更新版本

CVE-2020-15190 正在被利用嗎?

低 — EPSS 為 0.9%,目前沒有觀察到大規模利用活動。

受影響套件(3)

• from 0, < 1.15.4
• from 0, < 1.15.4
• from 0, < 1.15.4

CVSS 分數

參考連結(9)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2020-15190
• PATCHgithub.com/tensorflow/tensorflow
• WEBlists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
• WEBgithub.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-270.yaml