ChromeWeb browser · Google
CVE-2023-0703
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 DevTools in Google Chrome prior to 110.0.5481.77 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via UI interactions. (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 · moderate confidenceThis is a type confusion vulnerability in Google Chrome's DevTools that existed prior to version 110.0.5481.77. A remote attacker could exploit this by tricking a user into specific UI interactions within DevTools, potentially leading to heap corruption through the type confusion condition.
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
< 110.0.5481.77CVSS 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.
-
Check installed Chrome versionNavigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux) or 'chrome --version' (Windows) in a terminalAffected if The displayed version number is lower than 110.0.5481.77
-
Verify Chrome channelNavigate to chrome://settings/help and look for the channel indicator (Stable, Beta, Dev, Canary) or check via 'chrome://chrome-urls'Affected if Running a pre-Stable channel (Beta, Dev, or Canary) below version 110.0.5481.77, as these may receive updates on different schedules
-
Confirm DevTools accessibilityOpen DevTools by pressing F12, Ctrl+Shift+I, or right-clicking and selecting Inspect. Verify that DevTools interface loads successfully.Affected if DevTools is accessible and functional, as the vulnerability requires specific UI interactions within DevTools to be exploited
You are affected if your Chrome version is below 110.0.5481.77 AND you use or could be tricked into using DevTools on untrusted content.
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 · scoped110.0.5481.77
Update Google Chrome to version 110.0.5481.77 or later to remediate this vulnerability. Users should avoid engaging with untrusted DevTools interfaces from unknown sources.
Chrome 110.0.5481.77 or later
- Open Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is below 110.0.5481.77, Chrome will automatically check for and install updates
- Restart Chrome after the update completes
- Verify the version is now 110.0.5481.77 or later by returning to Help > About Google Chrome
- Alternatively, manually download and install the latest Chrome 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
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0703 — 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-2023-0703 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