ChromeWeb browser · Google
CVE-2023-0698
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 · uneditedOut of bounds read in WebRTC in Google Chrome prior to 110.0.5481.77 allowed a remote attacker to perform an out of bounds memory read 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 confidenceOut-of-bounds read vulnerability in WebRTC (Web Real-Time Communication) component of Google Chrome prior to version 110.0.5481.77. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing unauthorized memory reads outside allocated buffers and potential information disclosure.
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.
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if The displayed version is lower than 110.0.5481.77 (for example, 109.0.5494.112 or earlier).
-
Check Chrome version via command lineOn Windows, open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The reported version number is less than 110.0.5481.77.
-
Verify WebRTC availability (no mitigation needed)WebRTC is built into Chrome and cannot be disabled through user settings. No configuration check is required - the component is present in all standard Chrome installations.Affected if This check is always true for standard Chrome installations. The vulnerability applies if the version check shows an affected version.
You are affected if your installed Google Chrome version is below 110.0.5481.77, regardless of configuration, since the vulnerable WebRTC component is always present in standard Chrome installations.
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. Apply via standard endpoint management tools (e.g., group policy, SCCM, Intune) and verify deployment.
Chrome 110.0.5481.77 or later
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- Chrome will automatically check for and download any available updates
- If version 110.0.5481.77 or later is available, click 'Restart' to complete the update
- Alternatively, download the latest Chrome version from the official Google Chrome website (chrome.google.com) and install it
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0698 — 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-0698 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