Buffer overflow in Google Tensorflow

CVE-2020-15205

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 code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Vulnerability class: Buffer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.0 (Critical). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.010 (62.3th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 62nd percentile — 62.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-15205: held from 0.010 to 0.010.

EPSS over last 30 days · oldest: 0.010 · newest: 0.010 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2020-15205?
CVE-2020-15205 is a critical-severity vulnerability in Google Tensorflow, classified under Improper Restriction of Operations within the Bounds of a Memory Buffer. CVSS score: 9.0/10. Published 2020-09-25.
How severe is CVE-2020-15205?
Critical severity. CVSS v3 base score is 9.0 out of 10.