cve.bz

CVE-2022-29204 google tensorflow: Integer Underflow (Wrap or Wraparound)

5.5 mediumExploit referenceEPSS 0.4%Fix available

Medium (5.5) in google tensorflow. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.6.4, 2.7.2, 2.8.1.

On this page
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.UnsortedSegmentJoin` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `num_segments` is a positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-191 Integer Underflow (Wrap or Wraparound)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-29204 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-29204?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-29204?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-29204 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
google:tensorflowfrom 1.15.0 before 2.6.4
google:tensorflowfrom 2.7.0 before 2.7.2
google:tensorflow2.7.0:rc0
google:tensorflow2.7.0:rc1
google:tensorflow2.8.0
google:tensorflow2.8.0:rc0
google:tensorflow2.8.0:rc1
google:tensorflow2.9.0:rc0
google:tensorflow2.9.0:rc1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hx9q-2mx4-m4pgPyPItensorflow<2.6.42.6.4
GHSA-hx9q-2mx4-m4pgPyPItensorflow>=2.7.0 <2.7.22.7.2
GHSA-hx9q-2mx4-m4pgPyPItensorflow>=2.8.0 <2.8.12.8.1
GHSA-hx9q-2mx4-m4pgPyPItensorflow-cpu<2.6.42.6.4
GHSA-hx9q-2mx4-m4pgPyPItensorflow-cpu>=2.7.0 <2.7.22.7.2
GHSA-hx9q-2mx4-m4pgPyPItensorflow-cpu>=2.8.0 <2.8.12.8.1
GHSA-hx9q-2mx4-m4pgPyPItensorflow-gpu<2.6.42.6.4
GHSA-hx9q-2mx4-m4pgPyPItensorflow-gpu>=2.7.0 <2.7.22.7.2
GHSA-hx9q-2mx4-m4pgPyPItensorflow-gpu>=2.8.0 <2.8.12.8.1
PYSEC-2026-1010PyPItensorflow-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
PYSEC-2026-3203PyPItensorflow<2.6.4
>=2.7.0 <2.7.2
>=2.8.0 <2.8.1
2.6.4, 2.7.2, 2.8.1
PYSEC-2026-3342PyPItensorflow-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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON