ChromeWeb browser · Google
CVE-2023-4077
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 · uneditedInsufficient data validation in Extensions in Google Chrome prior to 115.0.5790.170 allowed an attacker who convinced a user to install a malicious extension to inject scripts or HTML into a privileged page via a crafted Chrome Extension. (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 confidenceInsufficient data validation in Chrome's extension system prior to version 115.0.5790.170 allows a malicious extension installed by an attacker to inject arbitrary scripts or HTML into privileged browser pages, enabling privilege escalation within the extension context.
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
< 115.0.5790.170CVSS 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 versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the current version numberAffected if The displayed version is lower than 115.0.5790.170
-
Review installed extensionsNavigate to chrome://extensions and examine all enabled extensions for any unknown, suspicious, or recently added extensions that you did not intentionally installAffected if Any extension exists that you did not authorize or that has elevated permissions beyond its stated purpose
-
Check for developer mode extensionsIn chrome://extensions, enable 'Developer mode' and inspect any unpacked extensions or those loaded from non-Web Store sourcesAffected if Developer mode is active with extensions loaded from unknown local paths or non-verified sources
-
Audit extension permissionsIn chrome://extensions, click 'Details' on each extension and review granted permissions, looking for excessive access to browsing data, tabs, or privileged URLsAffected if Any extension possesses permissions that appear unnecessary or allow access to privileged browser pages
You are affected if your Chrome version is below 115.0.5790.170 AND a malicious or unauthorized extension has been installed with elevated permissions.
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 · scoped115.0.5790.170
Update Google Chrome to version 115.0.5790.170 or later to remediate the insufficient data validation in the extensions subsystem.
Chrome 115.0.5790.170 or later
- Open Google Chrome
- Navigate to Chrome Menu (three dots) > Help > About Google Chrome
- Chrome will automatically check for updates
- If an update is available, click 'Update Google Chrome'
- Restart Chrome to complete the installation
- Verify the version is 115.0.5790.170 or later by returning to Help > About Google 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
- 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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4077 — 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-4077 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