dbcve.org
ChromeWeb browser · Google

CVE-2023-6706

HIGH · 8.8 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 120.0.6099.109 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Use after free in FedCM in Google Chrome prior to 120.0.6099.109 allowed a remote attacker who convinced a user to engage in specific UI interaction to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

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 use-after-free vulnerability exists in the FedCM (Federated Credential Management) API in Google Chrome versions prior to 120.0.6099.109. An attacker can trigger this flaw by persuading a user to perform specific UI interactions on a crafted HTML page, potentially leading to heap corruption and remote code execution.

MitigationUpdate Google Chrome to version 120.0.6099.109 or later to patch the vulnerability. Organizations should ensure automated patch management deploys this Chrome security update to all endpoints.

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:< 120.0.6099.109

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
High
Integrity
High
Availability
High

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

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
    Open chrome://version in the Chrome browser address bar and note the version number displayed, or access Chrome menu > Help > About Google Chrome
    Affected if The displayed version is lower than 120.0.6099.109
  2. Verify FedCM availability
    Navigate to chrome://flags in the address bar and search for 'FedCM' or 'Federated Credential Management' to confirm whether the feature flag is present and accessible
    Affected if The FedCM feature flag exists and is accessible in chrome://flags (indicating the feature is compiled into this build)
  3. Confirm FedCM is enabled
    In chrome://flags, check if the FedCM or Identity Provider API flag is set to Enabled rather than Default or Disabled
    Affected if FedCM is explicitly enabled or set to Default (which may enable it depending on rollout percentage)
  4. Determine if browser profile supports FedCM
    FedCM typically requires a signed-in Chrome profile with sync enabled; verify if the active profile is signed in by checking the account avatar in the top-right corner
    Affected if The browser profile is signed into a Google account with sync enabled

You are affected if your Chrome version is below 120.0.6099.109 AND the FedCM feature is compiled into your build AND a user with an active signed-in profile interacts with FedCM-enabled identity provider pages.

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

Update Google Chrome to version 120.0.6099.109 or later to patch the vulnerability. Organizations should ensure automated patch management deploys this Chrome security update to all endpoints.

Recommended fix High confidence

Chrome 120.0.6099.109 or later (any stable release beyond 120.0.6099.109)

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. Chrome will automatically check for updates; if available, click 'Update Google Chrome'
  6. Restart the browser to apply the update
  7. Alternatively, download the latest stable version directly from google.com/chrome

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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