dbcve.org
ChromeWeb browser · Google

CVE-2023-5487

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-11
Fix available
A fix is available. Upgrade to 118.0.5993.70 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
Inappropriate implementation in Fullscreen in Google Chrome prior to 118.0.5993.70 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension. (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 Chrome's Fullscreen API implementation prior to version 118.0.5993.70 allows a maliciously crafted Chrome extension to bypass navigation restrictions. An attacker must first convince a user to install the malicious extension for this attack to succeed.

MitigationUpdate Google Chrome to version 118.0.5993.70 or later. Organizations should review and restrict extension installation permissions via enterprise policies to limit exposure to malicious 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:< 118.0.5993.70
FedoraOperating system
Affected:= 37= 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 Google Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help
    Affected if Version displayed is less than 118.0.5993.70
  2. Verify Chrome extension installation policy
    Check if user-installed extensions are allowed. On managed systems, look for policy 'ExtensionInstallForcelist' or 'ExtensionInstallSources' in Chrome policy settings (Windows: gpedit.msc or registry, Mac: defaults, Linux: JSON policy files in /etc/opt/chrome/policies/)
    Affected if Users can install arbitrary extensions from the Chrome Web Store without administrative restriction
  3. Review installed Chrome extensions
    Navigate to chrome://extensions/ and review the list of installed extensions. Check for any unknown, untrusted, or recently added extensions
    Affected if Any extension is installed that was not explicitly approved by your organization
  4. Check Fedora Chrome package version (Fedora only)
    Run command: rpm -qa | grep google-chrome on Fedora 37 or 38 systems
    Affected if Package version is less than 118.0.5993.70

You are affected if you are running Google Chrome version below 118.0.5993.70 and either have untrusted extensions installed or users can install extensions without administrative review.

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 118.0.5993.70 or later
Fixed in 118.0.5993.70
Interim mitigation

Update Google Chrome to version 118.0.5993.70 or later. Organizations should review and restrict extension installation permissions via enterprise policies to limit exposure to malicious extensions.

Recommended fix High confidence

Chrome 118.0.5993.70 or later

  1. Open Chrome and navigate to chrome://settings/help to check your current version
  2. Chrome should automatically update to the latest version (118.0.5993.70 or later); if not, download the latest stable build from google.com/chrome
  3. Restart Chrome after the update completes
  4. Verify the version shows 118.0.5993.70 or higher under chrome://settings/help

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5487 — 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-5487 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