ChromeWeb browser · Google

CVE-2022-4439

HIGH · 8.8 CVSS v3.1 Published 2022-12-14

Fix available

A fix is available. Upgrade to 108.0.5359.124 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Use after free in Aura in Google Chrome on Windows prior to 108.0.5359.124 allowed a remote attacker who convinced the user to engage in specific UI interactions to potentially exploit heap corruption via specific UI interactions. (Chromium security severity: High)

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in Google Chrome's Aura UI framework on Windows. The flaw allows a remote attacker to potentially exploit heap corruption via specific UI interactions, enabling arbitrary code execution through memory that is accessed after being freed.

MitigationUpdate Google Chrome to version 108.0.5359.124 or later on all affected Windows systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 108.0.5359.124

CVSS breakdown

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?

dbcve checks

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

Verify Google Chrome is installed on Windows

Check for Chrome installation by looking for chrome.exe in typical locations: C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\, or check via Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome

Affected if Chrome is not found on the Windows system, the system is not affected by this specific CVE which only affects Chrome on Windows
Determine installed Chrome version

Open Chrome, click the three-dot menu, select Help > About Google Chrome, or navigate to chrome://settings/help, or run the command 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version' in Command Prompt

Affected if Unable to retrieve a version number means Chrome version cannot be determined for this check
Compare version against affected range

Compare the installed version number (e.g., 108.0.5359.124) to the affected range: any version below 108.0.5359.124 is vulnerable

Affected if Installed version is less than 108.0.5359.124 (for example, 108.0.5359.71 or 107.x.x.x)

A Windows system running Google Chrome version 108.0.5359.124 or higher is NOT affected; versions below 108.0.5359.124 ARE affected by this use-after-free vulnerability in the Aura UI framework.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 108.0.5359.124 or later

Fixed in 108.0.5359.124

Interim mitigation

Update Google Chrome to version 108.0.5359.124 or later on all affected Windows systems.

Recommended fix High confidence

Chrome 108.0.5359.124 or later

Open Chrome and navigate to chrome://settings/help to check the current version
Click 'Update Google Chrome' if an update is available, or manually download Chrome version 108.0.5359.124 or later from the official Chrome download page
Restart Chrome after the update completes
Verify the version by returning to chrome://settings/help and confirming the version is 108.0.5359.124 or higher

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

Fix this in Chrome Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing1.0 h
Review / QA1.0 h

4.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-4439 — 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

Primary sources

chromereleases.googleblog.comRelease NotesVendor Advisory
crbug.comPermissions RequiredVendor Advisory
security.gentoo.org
security.gentoo.org
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-4439?

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.

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

At a glance

A fix existsUpgrade to 108.0.5359.124 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-4439 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References