dbcve.org
ChromeWeb browser · Google

CVE-2024-11114

HIGH · 8.3 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 131.0.6778.69 or later.
See remediation →
90/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
Inappropriate implementation in Views in Google Chrome on Windows prior to 131.0.6778.69 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 the Views component (Chrome's UI framework) of Google Chrome on Windows allowed a remote attacker who had already compromised the renderer process to potentially escape the sandbox via a crafted HTML page. This is a privilege escalation from the already-sandboxed renderer to the broader system.

MitigationUpdate Google Chrome for Windows to version 131.0.6778.69 or later to patch the Views component vulnerability.

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

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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. Confirm Google Chrome is installed on Windows
    Check for chrome.exe in typical installation paths (C:\Program Files\Google\Chrome\Application\ or C:\Users\%USERNAME%\AppData\Local\Google\Chrome\Application\) or verify via registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Google Chrome browser is present on the Windows system
  2. Identify installed Chrome version number
    Open chrome://version in the Chrome browser address bar, or run the command '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' or '"C:\Users\%USERNAME%\AppData\Local\Google\Chrome\Application\chrome.exe" --version' from Command Prompt
    Affected if The displayed version is earlier than 131.0.6778.69 (for example, 131.0.6778.64 or any version below 131.0.6778.69)
  3. Confirm Windows platform is affected
    Verify the operating system is Windows by running 'winver' or checking system properties - the vulnerability specifically affects Chrome on Windows, not other platforms
    Affected if Running any version of Chrome below 131.0.6778.69 on Windows operating system
  4. Verify Views component is in use
    The Views component is Chrome's UI framework used for browser interface elements (tabs, address bar, menus). Any normal Chrome usage on Windows invokes this component automatically when rendering the browser chrome
    Affected if Using Chrome normally on Windows displays UI elements rendered through the Views component

A Windows user is affected if their installed Google Chrome version is below 131.0.6778.69, as this specific version range contains the vulnerability in the Views component that enables sandbox escape.

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

Update Google Chrome for Windows to version 131.0.6778.69 or later to patch the Views component vulnerability.

Recommended fix High confidence

Chrome 131.0.6778.69 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is below 131.0.6778.69, click 'Update Google Chrome' to download and install the latest version
  3. Restart the browser to apply the update
  4. Verify the update was successful by revisiting chrome://settings/help and confirming the version is 131.0.6778.69 or later

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-2024-11114 — 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-2024-11114 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