ChromeWeb browser · Google
CVE-2024-4671
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 · uneditedUse after free in Visuals in Google Chrome prior to 124.0.6367.201 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceUse-after-free vulnerability in Chrome's Visuals (rendering) component allows a remote attacker with an already-compromised renderer process to potentially escape the sandbox via a crafted HTML page, achieving code execution outside the sandbox.
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
< 124.0.6367.201
FedoraOperating system
= 38= 39= 40CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is lower than 124.0.6367.201
-
Confirm Chrome is using the affected Visuals componentThe Visuals component (rendering engine) is always active in Chrome; no specific flag or setting needs to be enabled for this vulnerability - it affects the core rendering processAffected if Chrome browser is running any version below 124.0.6367.201
-
Check if running on Fedora and its versionRun 'cat /etc/fedora-release' or 'rpm -q fedora-release'Affected if Running Fedora 38, 39, or 40 with an unpatched Chrome package
You are affected if Google Chrome version is below 124.0.6367.201, or if you are on Fedora 38/39/40 with an unpatched Chrome installation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped124.0.6367.201
Update Google Chrome to version 124.0.6367.201 or later. For enterprise deployments, push the update via centralized patch management and verify completion across all endpoints.
Chrome 124.0.6367.201 or later (stable channel)
- For Chrome Browser: Navigate to chrome://settings/help and click 'Update Google Chrome', or download the latest version from official Google Chrome channels (google.com/chrome)
- For Fedora systems: Run 'sudo dnf update google-chrome-stable' to receive the patched package
- Alternatively, wait for automatic updates if auto-update is enabled
- Verify the update by navigating to chrome://settings/help and confirming the version is 124.0.6367.201 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-4671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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