ChromeWeb browser · Google
CVE-2023-2458
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 · uneditedUse after free in ChromeOS Camera in Google Chrome on ChromeOS prior to 113.0.5672.114 allowed a remote attacker who convinced a user to engage in specific UI interaction to potentially exploit heap corruption via UI interaction. (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 confidenceUse after free vulnerability in ChromeOS Camera in Google Chrome on ChromeOS prior to version 113.0.5672.114 allows a remote attacker who tricks a user into specific UI interactions to potentially exploit heap corruption, leading to arbitrary code execution or denial of service.
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
< 113.0.5672.114CVSS 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.
-
Identify if the system is running ChromeOSCheck the operating system by looking at system information orAbout page in Chrome settings. On ChromeOS, the OS name will display as ChromeOS or Chromium OS.Affected if The system is not ChromeOS - this CVE only affects ChromeOS, not other Chrome versions on Windows/Mac/Linux
-
Determine the installed Google Chrome version on ChromeOSOpen Chrome, click the three-dot menu, go to Help > About Google Chrome. The version number is displayed on this page.Affected if The installed version is less than 113.0.5672.114
-
Confirm ChromeOS Camera is accessibleOpen the Camera app from the app launcher or verify camera.google特效 is accessible in Chrome. On ChromeOS, the Camera app is a built-in application.Affected if Camera app is present and accessible - the vulnerability exists in the ChromeOS Camera component
-
Check for recent Chrome browser usageReview browser history or recent session activity to see if Chrome has been actively used, as the exploit requires user interaction with specific UI elements.Affected if Chrome browser is actively used and the user could be tricked into the specific UI interactions required to trigger the vulnerability
A user is affected if they are running Google Chrome on ChromeOS with a version lower than 113.0.5672.114 and have access to the Camera functionality.
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 · scoped113.0.5672.114
Update Google Chrome on ChromeOS to version 113.0.5672.114 or later to patch the use-after-free vulnerability.
Chrome on ChromeOS 113.0.5672.114 or later
- Open Chrome browser on your ChromeOS device
- Navigate to Settings (three dots menu > Settings)
- Click on 'About Chrome' in the left sidebar
- Chrome will automatically check for updates
- If an update is available, click 'Restart' to apply the update
- Alternatively, you can run 'updateChrome' command from ChromeOS shell ( Crosh ) if needed
- After restart, verify version is 113.0.5672.114 or later by checking About Chrome
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-2458 — 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-2458 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