cve.bz

CVE-2023-25667 google tensorflow: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.5 highEPSS 0.3%Fix available

High (7.5) in google tensorflow. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.11.1.

On this page
TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when `2^31 <= num_frames * height * width * channels < 2^32`, for example Full HD screencast of at least 346 frames. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-02-19. 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-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
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-2023-25667 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-25667?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-25667?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-2023-25667 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:tensorflowbefore 2.12.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fqm2-gh8w-gr68PyPItensorflow<2.11.12.11.1
GHSA-fqm2-gh8w-gr68PyPItensorflow-cpu<2.11.12.11.1
GHSA-fqm2-gh8w-gr68PyPItensorflow-gpu<2.11.12.11.1
PYSEC-2026-1961PyPItensorflow-gpu<2.11.12.11.1
PYSEC-2026-3176PyPItensorflow<2.11.12.11.1
PYSEC-2026-3321PyPItensorflow-cpu<2.11.12.11.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux2tensorflow2.11.1-1AZL-31198
Azure Linux3tensorflow2.11.1-1AZL-35312

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON