cve.bz

CVE-2023-5849 Year 2038 problem, Y2K38, Y2038, Epochalypse

8.8 highEPSS 1.2%

High (8.8). EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
Integer overflow in USB in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
1.2% (unchanged from 1.2% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th 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: total, assessed 2025-04-23. 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-5849 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-5849?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-5849?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-5849 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 CNA's record in the CVE List.

ProductAffected
Google Chromefrom 119.0.6045.105 before 119.0.6045.105

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11chromium119.0.6045.105-1~deb11u1DSA-5546-1
Debian12chromium119.0.6045.105-1~deb12u1DEBIAN-CVE-2023-5849 DSA-5546-1
Debian13, 14chromium119.0.6045.105-1DEBIAN-CVE-2023-5849
SUSEPackage Hub 15 SP4, Package Hub 15 SP5chromium119.0.6045.123-bp155.2.55.1openSUSE-SU-2023:0368-1
SUSEPackage Hub 15 SP4, Package Hub 15 SP5gn0.20231023-bp155.5.3.1openSUSE-SU-2023:0368-1
openSUSELeap 15.4, Leap 15.5chromium119.0.6045.123-bp155.2.55.1openSUSE-SU-2023:0368-1
openSUSELeap 15.4, Leap 15.5gn0.20231023-bp155.5.3.1openSUSE-SU-2023:0368-1
openSUSETumbleweedchromium119.0.6045.123-1.1openSUSE-SU-2024:13419-1 openSUSE-SU-2024:13423-1
Alpinev3.18qt5-qtwebengine5.15.13-r10ALPINE-CVE-2023-5849
Alpinev3.19, v3.20, v3.21 and 2 moreqt5-qtwebengine5.15.15-r5ALPINE-CVE-2023-5849
Alpinev3.19, v3.20, v3.21 and 3 moreqt6-qtwebengine6.6.0-r2ALPINE-CVE-2023-5849

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE · Alpine.

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