ChromeWeb browser · Google
CVE-2024-10230
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 · uneditedType Confusion in V8 in Google Chrome prior to 130.0.6723.69 allowed a remote attacker 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 confidenceType confusion vulnerability in Google Chrome's V8 JavaScript engine (versions prior to 130.0.6723.69) allows remote attackers to exploit heap corruption through malicious HTML pages. This memory corruption flaw can be triggered when a user visits a specially crafted webpage, potentially leading to arbitrary code execution.
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
< 130.0.6723.69CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate installed Chrome versionOpen Google Chrome, click the three-dot menu (top right), select Help, then select About Google Chrome. Alternatively, type chrome://version in the address bar and press Enter.Affected if The version displayed is less than 130.0.6723.69
-
Verify full version numberOn the chrome://version page, note the complete version string shown next to 'Version'. It follows the format X.X.X.X (for example, 130.0.6723.58).Affected if The four-part version number is lower than 130.0.6723.69 when compared numerically part by part
-
Check if auto-updates are activeOn chrome://version page, look for 'Update status' or check if a newer version is available. On Windows, you can also check via Help > About Google Chrome to see if updates are pending.Affected if Chrome reports an available update or shows a version number below 130.0.6723.69, indicating the browser has not yet been patched
You are affected if your installed Google Chrome version is any build earlier than 130.0.6723.69, as this CVE exploits a type confusion flaw in the V8 JavaScript engine present in those older versions.
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 · scoped130.0.6723.69
Update Google Chrome to version 130.0.6723.69 or later. Organizations should deploy browser updates via patch management and verify completion across endpoints.
Chrome 130.0.6723.69 or later
- Open Google Chrome browser
- Click the menu icon (three dots) in the top right corner
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates and automatically download version 130.0.6723.69 or later
- Click 'Relaunch' or manually restart the browser to apply the update
- Confirm the version by returning to 'About Google Chrome' and verifying it shows 130.0.6723.69 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10230 — 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-10230 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