dbcve.org
ChromeWeb browser · Google

CVE-2024-11112

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 131.0.6778.69 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 Media in Google Chrome on Windows prior to 131.0.6778.69 allowed a remote attacker to potentially exploit heap corruption 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 use-after-free vulnerability in the Media component of Google Chrome on Windows versions prior to 131.0.6778.69 allows a remote attacker to exploit heap corruption via a specially crafted HTML page. The vulnerability stems from the application continuing to access memory after it has been freed, leading to potential arbitrary code execution.

MitigationUpdate Google Chrome to version 131.0.6778.69 or later. In enterprise environments, deploy the browser update through standard endpoint management tooling and verify completion across affected Windows systems.

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
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. Verify Google Chrome is installed on Windows
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Chrome*"}' in PowerShell to check for Chrome installation.
    Affected if Google Chrome is not found in the system registry or program files.
  2. Check installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser address bar, or run 'Get-ItemProperty "C:\Program Files\Google\Chrome\Application\chrome.exe" | Select-Object -ExpandProperty VersionInfo' in PowerShell to retrieve the version number.
    Affected if The displayed version number is lower than 131.0.6778.69.
  3. Confirm Windows platform
    Verify the operating system is Windows by running 'systeminfo | findstr /B /C:"OS Name"' in Command Prompt or checking System Properties.
    Affected if The system is running an operating system other than Windows - this CVE only affects Chrome on Windows.
  4. Check if Media component is in use
    This vulnerability affects the Media component which is a core part of Chrome. No specific configuration check is required - any use of media playback features (video/audio in web pages) could trigger the vulnerable code path.
    Affected if Chrome with an affected version is used to browse web pages containing media content.

You are affected if Google Chrome is installed on Windows and the installed version is lower than 131.0.6778.69.

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 to version 131.0.6778.69 or later. In enterprise environments, deploy the browser update through standard endpoint management tooling and verify completion across affected Windows systems.

Recommended fix High confidence

Chrome 131.0.6778.69 or later (Windows)

  1. Open Google Chrome on Windows
  2. Click the three-dot menu icon in the upper right corner
  3. Select 'Settings' from the dropdown menu
  4. Click 'About Chrome' in the left sidebar
  5. Chrome will automatically check for updates; if an update is available, it will begin downloading
  6. Once the update is downloaded, click 'Restart' to apply the update
  7. Verify the version by returning to 'About Chrome' and confirming version 131.0.6778.69 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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