ChromeWeb browser · Google
CVE-2023-1812
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 memory access in DOM Bindings in Google Chrome prior to 112.0.5615.49 allowed a remote attacker to perform out of bounds memory access 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 confidenceThis is an out-of-bounds memory access vulnerability in the DOM Bindings component of Google Chrome versions prior to 112.0.5615.49. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially allowing reading or writing beyond allocated memory boundaries.
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
< 112.0.5615.49
FedoraOperating system
= 36= 37
Debian LinuxOperating system
= 11.0CVSS 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 if Google Chrome is installedRun 'google-chrome --version' on Linux, or open Chrome and navigate to 'chrome://version' to view the installed versionAffected if Google Chrome is present on the system
-
Verify the installed Chrome version numberCompare the displayed version to 112.0.5615.49. On Linux you can also use 'rpm -q google-chrome-stable' or 'dpkg -l | grep -i chrome' to query the package versionAffected if The installed version is older than 112.0.5615.49 (for example 112.0.5615.48 or any prior version)
-
Confirm the DOM Bindings component is in useThe vulnerability affects the DOM Bindings component which is part of Chrome's rendering engine. This component is automatically loaded when browsing any webpageAffected if Chrome is used to browse web content, which is the default behavior
A user is affected if Google Chrome (any variant) version 112.0.5615.49 or later is NOT installed on the system.
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 · scoped112.0.5615.49
Update Google Chrome to version 112.0.5615.49 or later. In enterprise environments, deploy the update through centralized patch management and verify complete coverage across the browser fleet.
Chrome 112.0.5615.49 or later (or latest stable release)
- 1. Open Google Chrome browser
- 2. Navigate to Chrome Settings > Help > About Google Chrome
- 3. Chrome will automatically check for and install updates
- 4. If update is available to version 112.0.5615.49 or later, allow the update to install
- 5. Restart the browser to complete the update
- 6. Alternatively, download the latest Chrome version from the official Google Chrome website
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1812 — 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-1812 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