cve.bz

CVE-2022-21731 google tensorflow: Type Confusion

6.5 mediumExploit referenceEPSS 0.9%Fix available

Medium (6.5) in google tensorflow. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.5.3, 2.6.3, 2.7.1.

On this page
Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `ConcatV2` can be used to trigger a denial of service attack via a segfault caused by a type confusion. The `axis` argument is translated into `concat_dim` in the `ConcatShapeHelper` helper function. Then, a value for `min_rank` is computed based on `concat_dim`. This is then used to validate that the `values` tensor has at least the required rank. However, `WithRankAtLeast` receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that `min_rank` is a 32-bits value and the value of `axis`, the `rank` argument is a negative value, so the error check is bypassed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th 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-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-21731 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-21731?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-21731?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-21731 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:tensorflowthrough 2.5.2
google:tensorflowfrom 2.6.0 through 2.6.2
google:tensorflow2.7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m4hf-j54p-p353PyPItensorflow<2.5.32.5.3
GHSA-m4hf-j54p-p353PyPItensorflow>=2.6.0 <2.6.32.6.3
GHSA-m4hf-j54p-p353PyPItensorflow>=2.7.0 <2.7.12.7.1
GHSA-m4hf-j54p-p353PyPItensorflow-cpu<2.5.32.5.3
GHSA-m4hf-j54p-p353PyPItensorflow-cpu>=2.6.0 <2.6.32.6.3
GHSA-m4hf-j54p-p353PyPItensorflow-cpu>=2.7.0 <2.7.12.7.1
GHSA-m4hf-j54p-p353PyPItensorflow-gpu<2.5.32.5.3
GHSA-m4hf-j54p-p353PyPItensorflow-gpu>=2.6.0 <2.6.32.6.3
GHSA-m4hf-j54p-p353PyPItensorflow-gpu>=2.7.0 <2.7.12.7.1
PYSEC-2022-110PyPItensorflow-gpu<2.5.3
>=2.6.0 <2.6.3
2.5.3, 2.6.3
PYSEC-2022-55PyPItensorflow-cpu<2.5.3
>=2.6.0 <2.6.3
2.5.3, 2.6.3
PYSEC-2026-3211PyPItensorflow<2.5.3
>=2.6.0 <2.6.3
>=2.7.0 <2.7.1
2.5.3, 2.6.3, 2.7.1

References

Check your stackJSON