What is CVE-2020-15195?

CVE-2020-15195 is a medium-severity out-of-bounds write vulnerability in tensorflow (pip), affecting versions < 1.15.4. It is fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1. A write operation targets a memory location beyond the intended buffer boundary.

How severe is CVE-2020-15195?

CVE-2020-15195 has a CVSS score of 8.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2020-15195?

tensorflow (pip) versions < 1.15.4; tensorflow-cpu (pip) versions < 1.15.4; tensorflow-gpu (pip) versions < 1.15.4.

Is there a fix for CVE-2020-15195?

Yes. CVE-2020-15195 is fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1. Upgrade to this version or later.

Is CVE-2020-15195 exploitable, and should I be worried?

Whether CVE-2020-15195 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-15195 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-15195?

Upgrade: tensorflow to 1.15.4 or later, tensorflow to 2.0.3 or later, tensorflow to 2.1.2 or later, tensorflow to 2.2.1 or later, tensorflow to 2.3.1 or later, tensorflow-cpu to 1.15.4 or later, tensorflow-cpu to 2.0.3 or later, tensorflow-cpu to 2.1.2 or later, tensorflow-cpu to 2.2.1 or later, tensorflow-cpu to 2.3.1 or later, tensorflow-gpu to 1.15.4 or later, tensorflow-gpu to 2.0.3 or later, tensorflow-gpu to 2.1.2 or later, tensorflow-gpu to 2.2.1 or later, tensorflow-gpu to 2.3.1 or later.

CVE-2020-15195 in tensorflow

Q: How severe is CVE-2020-15195?

CVE-2020-15195 has a CVSS score of 8.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2020-15195?

tensorflow (pip) versions < 1.15.4; tensorflow-cpu (pip) versions < 1.15.4; tensorflow-gpu (pip) versions < 1.15.4.

Q: Is there a fix for CVE-2020-15195?

Yes. CVE-2020-15195 is fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1. Upgrade to this version or later.

Q: Is CVE-2020-15195 exploitable, and should I be worried?

Whether CVE-2020-15195 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-15195 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-15195?

Upgrade: tensorflow to 1.15.4 or later, tensorflow to 2.0.3 or later, tensorflow to 2.1.2 or later, tensorflow to 2.2.1 or later, tensorflow to 2.3.1 or later, tensorflow-cpu to 1.15.4 or later, tensorflow-cpu to 2.0.3 or later, tensorflow-cpu to 2.1.2 or later, tensorflow-cpu to 2.2.1 or later, tensorflow-cpu to 2.3.1 or later, tensorflow-gpu to 1.15.4 or later, tensorflow-gpu to 2.0.3 or later, tensorflow-gpu to 2.1.2 or later, tensorflow-gpu to 2.2.1 or later, tensorflow-gpu to 2.3.1 or later.

Summary

Heap buffer overflow in Tensorflow

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

Impact

The implementation of SparseFillEmptyRowsGrad uses a double indexing pattern:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L263-L269

It is possible for reverse_index_map(i) to be an index outside of bounds of grad_values, thus resulting in a heap buffer overflow.

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2020-15195 has a CVSS score of 8.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1); upgrading removes the vulnerable code path.

Affected versions

tensorflow (< 1.15.4) tensorflow (>= 2.0.0, < 2.0.3) tensorflow (>= 2.1.0, < 2.1.2) tensorflow (= 2.2.0) tensorflow (= 2.3.0) tensorflow-cpu (< 1.15.4) tensorflow-cpu (>= 2.0.0, < 2.0.3) tensorflow-cpu (>= 2.1.0, < 2.1.2) tensorflow-cpu (= 2.2.0) tensorflow-cpu (= 2.3.0) tensorflow-gpu (< 1.15.4) tensorflow-gpu (>= 2.0.0, < 2.0.3) tensorflow-gpu (>= 2.1.0, < 2.1.2) tensorflow-gpu (= 2.2.0) tensorflow-gpu (= 2.3.0)

Security releases

tensorflow → 1.15.4 (pip) tensorflow → 2.0.3 (pip) tensorflow → 2.1.2 (pip) tensorflow → 2.2.1 (pip) tensorflow → 2.3.1 (pip) tensorflow-cpu → 1.15.4 (pip) tensorflow-cpu → 2.0.3 (pip) tensorflow-cpu → 2.1.2 (pip) tensorflow-cpu → 2.2.1 (pip) tensorflow-cpu → 2.3.1 (pip) tensorflow-gpu → 1.15.4 (pip) tensorflow-gpu → 2.0.3 (pip) tensorflow-gpu → 2.1.2 (pip) tensorflow-gpu → 2.2.1 (pip) tensorflow-gpu → 2.3.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

We have patched the issue in 390611e0d45c5793c7066110af37c8514e6a6c54 and will release a patch release for all affected versions.

We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Frequently Asked Questions

What is CVE-2020-15195? CVE-2020-15195 is a medium-severity out-of-bounds write vulnerability in tensorflow (pip), affecting versions < 1.15.4. It is fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1. A write operation targets a memory location beyond the intended buffer boundary.
How severe is CVE-2020-15195? CVE-2020-15195 has a CVSS score of 8.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2020-15195?
- tensorflow (pip) (versions < 1.15.4)
- tensorflow-cpu (pip) (versions < 1.15.4)
- tensorflow-gpu (pip) (versions < 1.15.4)
Is there a fix for CVE-2020-15195? Yes. CVE-2020-15195 is fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1. Upgrade to this version or later.
Is CVE-2020-15195 exploitable, and should I be worried? Whether CVE-2020-15195 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-15195 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-15195?
- Upgrade tensorflow to 1.15.4 or later
- Upgrade tensorflow to 2.0.3 or later
- Upgrade tensorflow to 2.1.2 or later
- Upgrade tensorflow to 2.2.1 or later
- Upgrade tensorflow to 2.3.1 or later
- Upgrade tensorflow-cpu to 1.15.4 or later
- Upgrade tensorflow-cpu to 2.0.3 or later
- Upgrade tensorflow-cpu to 2.1.2 or later
- Upgrade tensorflow-cpu to 2.2.1 or later
- Upgrade tensorflow-cpu to 2.3.1 or later
- Upgrade tensorflow-gpu to 1.15.4 or later
- Upgrade tensorflow-gpu to 2.0.3 or later
- Upgrade tensorflow-gpu to 2.1.2 or later
- Upgrade tensorflow-gpu to 2.2.1 or later
- Upgrade tensorflow-gpu to 2.3.1 or later

Other vulnerabilities in tensorflow

CVE-IDSeverityPackage summary

CVE-2023-33976Hightensorflow: TensorFlow has segfault in array_ops.upper_bound CVE-2023-25661Mediumtensorflow: TensorFlow Denial of Service vulnerability CVE-2023-25659Hightensorflow: TensorFlow vulnerable to Out-of-Bounds Read in DynamicStitch CVE-2023-25660Hightensorflow: TensorFlow vulnerable to seg fault in `tf.raw_ops.Print`CVE-2023-25662Hightensorflow: TensorFlow vulnerable to integer overflow in EditDistance