Skip to content
Fencer Intel
medium 6.5

CVE-2019-9635 json

NULL Pointer Dereference in Google TensorFlow

published 7y ago modified 4mo ago also GHSA-mfg7-x5m7-6p8w , PYSEC-2019-210 , PYSEC-2019-228 , PYSEC-2019-235 , EUVD-2019-0143

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file.

Patch / fix

  • pypi tensorflow 1.12.1, 1.12.2
  • pypi tensorflow-gpu 1.12.1, 1.12.2
  • pypi tensorflow-cpu 1.12.2
  • google tensorflow 1.12.2

Is CVE-2019-9635 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
>=1.0.0, <1.12.1
<1.12.2
1.12.1
1.12.2
pypi tensorflow-gpu
>=1.0.0, <1.12.1
<1.12.2
1.12.1
1.12.2
pypi tensorflow-cpu
<1.12.2
1.12.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.