ChromeWeb browser · Google
CVE-2023-1813
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 · uneditedInappropriate implementation in Extensions in Google Chrome prior to 112.0.5615.49 allowed an attacker who convinced a user to install a malicious extension to bypass file access restrictions 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 vulnerability in Google Chrome extensions prior to version 112.0.5615.49 allowed a malicious extension to bypass file access restrictions through crafted HTML pages. An attacker would need to convince a user to install the malicious extension first, then exploit the flaw to access files outside the normal extension 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
< 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 your 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 112.0.5615.49 (e.g., 111.x, 110.x, etc.)
-
Check your operating system versionOn Fedora: run 'cat /etc/fedora-release' or 'fedora-release'. On Debian: run 'cat /etc/debian_version'.Affected if Running Fedora 36 or Fedora 37, or Debian 11.0, with an affected Chrome version installed via system package manager
-
Review installed extensionsOpen Chrome, navigate to chrome://extensions, toggle on 'Developer mode', then review each extension's name, publisher, and permissions. Look for unknown or suspicious extensions you do not recall installing.Affected if Any extension is present that you did not intentionally install, especially if it requests broad permissions such as file access, tabs, or scripting
You are affected if your Chrome version is below 112.0.5615.49 AND you have installed a malicious extension, as the vulnerability requires both conditions to be exploited.
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. Organizations should ensure automatic updates are enabled or deploy the update via enterprise management tools.
Chrome 112.0.5615.49 or later
- Update Google Chrome to version 112.0.5615.49 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome'
- Alternatively, download the latest stable Chrome from the official Google Chrome website
- For Fedora systems, run: sudo dnf update google-chrome-stable
- For Debian Linux 11, ensure Chrome is updated through system package manager or download latest .deb package from Google
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1813 — 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-1813 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