Skip to content
Fencer Intel
medium 6.5

CVE-2018-21233 json

Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory.

published 6y ago modified 4mo ago also GHSA-h98h-8mxr-m8gx , PYSEC-2020-253 , PYSEC-2020-269 , PYSEC-2020-304 , EUVD-2020-0185

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

Summary

TensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc.

Patch / fix

  • pypi tensorflow 1.7.0
  • pypi tensorflow-gpu 1.7.0
  • pypi tensorflow-cpu 1.7.0
  • google tensorflow 1.7.0

Is CVE-2018-21233 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.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<1.7.0
1.7.0
pypi tensorflow-gpu
<1.7.0
1.7.0
pypi tensorflow-cpu
<1.7.0
1.7.0

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.