Skip to content
Fencer Intel
high 7.1

CVE-2022-29208 json

Segfault and Out-of-bounds Write write due to incomplete validation in TensorFlow

published 4y ago modified 2mo ago also BIT-tensorflow-2022-29208 , EUVD-2022-2039 , GHSA-2r2f-g8mw-9gvr , PYSEC-2026-3088 , PYSEC-2026-3266 , PYSEC-2026-943

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
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.raw_ops.EditDistance` has incomplete validation. Users can pass negative values to cause a segmentation fault based denial of service. In multiple places throughout the code, one may compute an index for a write operation. However, the existing validation only checks against the upper bound of the array. Hence, it is possible to write before the array by massaging the input to generate negative values for `loc`. 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-29208 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.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2r2f-g8mw-9gvr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 3.6 AV:L/AC:L/Au:N/C:N/I:P/A:P
OSV 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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

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.