cve.bz

CVE-2022-23583 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. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. 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; 60th 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-843 Access of Resource Using Incompatible Type (Type Confusion)
CWE-617 Reachable Assertion
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-23583 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-23583?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-23583?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-23583 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-gjqc-q9g6-q2j3PyPItensorflow<2.5.32.5.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow>=2.6.0 <2.6.32.6.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow>=2.7.0 <2.7.12.7.1
GHSA-gjqc-q9g6-q2j3PyPItensorflow-cpu<2.5.32.5.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow-cpu>=2.6.0 <2.6.32.6.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow-cpu>=2.7.0 <2.7.12.7.1
GHSA-gjqc-q9g6-q2j3PyPItensorflow-gpu<2.5.32.5.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow-gpu>=2.6.0 <2.6.32.6.3
GHSA-gjqc-q9g6-q2j3PyPItensorflow-gpu>=2.7.0 <2.7.12.7.1
PYSEC-2022-147PyPItensorflow-gpu<2.5.3
>=2.6.0 <2.6.3
2.5.3, 2.6.3
PYSEC-2022-92PyPItensorflow-cpu<2.5.3
>=2.6.0 <2.6.3
2.5.3, 2.6.3
PYSEC-2026-3191PyPItensorflow<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