Skip to content
Fencer Intel
medium 5.5

CVE-2022-29211 json

Segfault in TensorFlow if `tf.histogram_fixed_width` is called with NaN values

published 4y ago modified 2mo ago also BIT-tensorflow-2022-29211 , EUVD-2022-5854 , GHSA-xrp2-fhq4-4q3w , PYSEC-2026-1048 , PYSEC-2026-3260 , PYSEC-2026-3382

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.histogram_fixed_width` is vulnerable to a crash when the values array contain `Not a Number` (`NaN`) elements. The implementation assumes that all floating point operations are defined and then converts a floating point result to an integer index. If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash. This only occurs on the CPU implementation. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.

Patch / fix

  • pypi tensorflow 2.6.4, 2.7.2, 2.8.1
  • pypi tensorflow-cpu 2.6.4, 2.7.2, 2.8.1
  • pypi tensorflow-gpu 2.6.4, 2.7.2, 2.8.1
  • bitnami tensorflow 2.6.4, 2.7.2, 2.8.1
  • google tensorflow 2.6.4, 2.7.2

Is CVE-2022-29211 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

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrp2-fhq4-4q3w referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/tensorflow/tensorflow/issues/45770 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.6.4
>=2.7.0, <2.7.2
>=2.8.0, <2.8.1
2.6.4
2.7.2
2.8.1
pypi tensorflow-cpu
<2.6.4
>=2.7.0, <2.7.2
>=2.8.0, <2.8.1
2.6.4
2.7.2
2.8.1
pypi tensorflow-gpu
<2.6.4
>=2.7.0, <2.7.2
>=2.8.0, <2.8.1
2.6.4
2.7.2
2.8.1
bitnami tensorflow
<2.6.4
>=2.7.0, <2.7.2
>=2.8.0, <2.8.1
2.6.4
2.7.2
2.8.1

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-20 Improper Input Validation

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.