dbcve.org
ChromeWeb browser · Google

CVE-2023-4367

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 116.0.5845.96 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient policy enforcement in Extensions API in Google Chrome prior to 116.0.5845.96 allowed an attacker who convinced a user to install a malicious extension to bypass an enterprise policy via a crafted HTML page. (Chromium security severity: Medium)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in Google Chrome's Extensions API allows a malicious extension, once installed, to bypass enterprise policy restrictions when rendering crafted HTML pages. The insufficient policy enforcement in the Extensions API prior to version 116.0.5845.96 enables the attack.

MitigationUpdate Chrome to version 116.0.5845.96 or later. Until the update is deployed, restrict user ability to install extensions and monitor for suspicious extensions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 116.0.5845.96
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 38

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux), or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties (Windows)
    Affected if The version number is less than 116.0.5845.96
  2. Check for installed extensions
    Navigate to chrome://extensions in the Chrome browser and review the list of installed extensions
    Affected if Any extensions are installed, especially unknown or suspicious ones
  3. Check enterprise policy status
    Navigate to chrome://policy in the Chrome browser and review the active policies, or check for policy files in /etc/opt/chrome/policies/ (Linux) or Windows Registry policies
    Affected if Enterprise policies are configured and enforced, as the vulnerability allows bypassing these restrictions
  4. Verify package version on Debian/Fedora
    Run 'dpkg -l | grep chrome' (Debian) or 'rpm -q chrome-browser' or 'rpm -q google-chrome-stable' (Fedora)
    Affected if The installed package version is below 116.0.5845.96

You are affected if Chrome version is below 116.0.5845.96 AND extensions are installed, especially in environments where enterprise policies are meant to restrict extension behavior.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 116.0.5845.96 or later
Fixed in 116.0.5845.96
Interim mitigation

Update Chrome to version 116.0.5845.96 or later. Until the update is deployed, restrict user ability to install extensions and monitor for suspicious extensions.

Recommended fix High confidence

Chrome 116.0.5845.96 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is below 116.0.5845.96, proceed with updating
  3. For Debian Linux: Run 'sudo apt-get update && sudo apt-get upgrade' or download Chrome from https://www.google.com/chrome/ and install the new version
  4. For Fedora: Run 'sudo dnf update' or download Chrome from https://www.google.com/chrome/ and install the new version
  5. Restart Chrome after the update completes
  6. Verify the version is 116.0.5845.96 or later by revisiting chrome://settings/help

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4367 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data