CVE-2023-1232 — Allocation of Resources Without Limits or Throttling in Google Chrome

CWE-770 — Allocation of Resources Without Limits or Throttling10 documents8 sources
Severity
4.3MEDIUMNVD
OSV8.8
EPSS
0.1%
top 79.51%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
8
Google ChromeChromiumDebian Chromium+5 more
Timeline
PublishedMar 7
Latest updateMar 14

Description

Insufficient policy enforcement in Resource Timing in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to obtain potentially sensitive information from API via a crafted HTML page. (Chromium security severity: Low)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NExploitability: 2.8 | Impact: 1.4

Affected Packages9 packages

▶CVEListV5google/chrome111.0.5563.64 — 111.0.5563.64
▶NVDgoogle/chrome< 111.0.5563.64
▶debiandebian/chromium< chromium 111.0.5563.64-1 (bookworm)
▶Debianchromium/chromium< 111.0.5563.64-1~deb11u1+3

🔴Vulnerability Details

3
OSV
chromium-browser vulnerabilities↗2023-03-13
▶
GHSA
GHSA-2rcf-2963-c47m: Insufficient policy enforcement in Resource Timing in Google Chrome prior to 111↗2023-03-08
▶
OSV
CVE-2023-1232: Insufficient policy enforcement in Resource Timing in Google Chrome prior to 111↗2023-03-07
▶

📋Vendor Advisories

5
Microsoft
Chromium: CVE-2023-1232 Insufficient policy enforcement in Resource Timing↗2023-03-14
▶
Microsoft
An issue was discovered in Dnsmasq before 2.90. The default maximum EDNS.0 UDP packet size was set to 4096 but should be 1232 because of DNS Flag Day 2020.↗2023-03-14
▶
Ubuntu
Chromium vulnerabilities↗2023-03-13
▶
Chrome
Stable Channel Update for Desktop: CVE-2023-1231↗2023-03-07
▶
Debian
CVE-2023-1232: chromium - Insufficient policy enforcement in Resource Timing in Google Chrome prior to 111...↗2023
▶