dbcve.org
ChromeWeb browser · Google

CVE-2022-2481

HIGH · 8.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 103.0.5060.134 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Views in Google Chrome prior to 103.0.5060.134 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via UI interaction.

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 confidence

Use after free vulnerability in Chrome's Views component prior to version 103.0.5060.134 allows a remote attacker who tricks a user into specific UI interactions to potentially exploit heap corruption via a use-after-free condition.

MitigationUpdate Google Chrome to version 103.0.5060.134 or later to obtain the patched binary; enterprises may need to push updates via endpoint management tools.

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
Affected:< 103.0.5060.134

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google Chrome is installed
    Check for Chrome executable in common installation paths: Windows: %ProgramFiles%\Google\Chrome\Application\chrome.exe or %LocalAppData%\Google\Chrome\Application\chrome.exe; macOS: /Applications/Google Chrome.app; Linux: /usr/bin/google-chrome or /usr/bin/chromium-browser
    Affected if Chrome browser is found on the system
  2. Retrieve installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'chrome --version' from command line, or check file version property of chrome.exe
    Affected if Unable to determine version or version is blank/not found
  3. Compare version to affected range
    Compare the installed version number to 103.0.5060.134 - ensure the full four-part version number is evaluated (e.g., 103.0.5060.53, 103.0.5060.0, 102.0.5005.124)
    Affected if Installed version is lower than 103.0.5060.134 (e.g., 103.0.5060.53 or any 102.x, 101.x release)
  4. Verify Chrome Views component is in use
    This vulnerability affects Chrome's Views UI framework. Normal browsing usage with standard HTML/CSS UI typically does not invoke Views; internal Chrome pages and some dialogs use Views. Check if user interacts with Chrome-specific UI dialogs (e.g., Downloads, Print preview, Settings pages accessed via chrome:// URLs)
    Affected if User regularly interacts with Chrome's native UI dialogs and dialogs are displayed using the Views framework

User is affected if Google Chrome version is lower than 103.0.5060.134 and the user can be tricked into specific UI interactions that invoke the Views component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 103.0.5060.134 or later
Fixed in 103.0.5060.134
Interim mitigation

Update Google Chrome to version 103.0.5060.134 or later to obtain the patched binary; enterprises may need to push updates via endpoint management tools.

Recommended fix High confidence

Chrome 103.0.5060.134 or later (stable channel)

  1. Check the current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
  2. If the installed version is earlier than 103.0.5060.134, click 'Update Google Chrome' button if presented
  3. Restart Chrome to complete the update
  4. Alternatively, download the latest Chrome version from the official Google Chrome website and reinstall
Caveat Minor Chrome updates typically have no user-facing breaking changes; however, older websites or extensions may experience temporary compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2481 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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