Skip to content
Fencer Vulns
medium 4.3

CVE-2023-4364 json

Inappropriate implementation in Permission Prompts in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to obfuscate security…

published 2023-08-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-54228

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

Inappropriate implementation in Permission Prompts in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to obfuscate security UI via a crafted HTML page. (Chromium security severity: Medium)

Patch / fix

  • google chrome 116.0.5845.96
  • chromium Debian 12 116.0.5845.96-1~deb12u1
  • chromium Debian 14, Debian 13 116.0.5845.96-1

debian advisories DEBIAN-CVE-2023-4364

  • chromium openSUSE Tumbleweed 116.0.5845.96-1.1
  • opera openSUSE Leap 15.4 NonFree 102.0.4880.40-lp154.2.50.1
  • chromium Package Hub 15 SP5, Package Hub 15 SP4, openSUSE Leap 15.5 +1 more 116.0.5845.96-bp155.2.19.1

opensuse advisories openSUSE-SU-2024:13139-1openSUSE-SU-2024:13144-1openSUSE-SU-2023:0251-1openSUSE-SU-2023:0234-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-4364 updated cvss 6.5

chromium-browser: Inappropriate implementation in Permission Prompts

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected products

  • Google Chrome

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.