dbcve.org
ChromeWeb browser · Google

CVE-2022-0799

HIGH · 8.8 CVSS v3.1 Published 2022-04-05
Fix available
A fix is available. Upgrade to 99.0.4844.51 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
Insufficient policy enforcement in Installer in Google Chrome on Windows prior to 99.0.4844.51 allowed a remote attacker to perform local privilege escalation via a crafted offline installer file.

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

This vulnerability in Google Chrome's Windows installer (versions prior to 99.0.4844.51) allows insufficient policy enforcement, enabling a remote attacker to perform local privilege escalation by tricking a user into running a crafted offline installer file. The attacker would need to deliver a malicious installer to the target system and convince the user to execute it, potentially resulting in elevated system privileges.

MitigationUpgrade Google Chrome to version 99.0.4844.51 or later on all Windows systems. Organizations should also implement controls to prevent users from running untrusted or offline installers and patch management processes to ensure timely browser updates.

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:< 99.0.4844.51

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. Check if Google Chrome is installed on Windows
    Open Command Prompt or PowerShell and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" or check C:\Program Files\Google\Chrome\Application\chrome.exe
    Affected if Chrome is found on the system
  2. Determine the installed Chrome version
    Run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version or right-click chrome.exe in File Explorer, select Properties, and check the Details tab for Product Version
    Affected if The displayed version is less than 99.0.4844.51
  3. Verify the installation method if possible
    Check the installer source by examining the Chrome installation directory for any setup or installer files, or review the original installation package used
    Affected if Chrome was installed using an offline installer package rather than via automatic updates or enterprise deployment with policy controls

If Chrome is installed on Windows and the version is below 99.0.4844.51, the system may be vulnerable if an attacker can trick a user into running a malicious offline installer.

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 99.0.4844.51 or later
Fixed in 99.0.4844.51
Interim mitigation

Upgrade Google Chrome to version 99.0.4844.51 or later on all Windows systems. Organizations should also implement controls to prevent users from running untrusted or offline installers and patch management processes to ensure timely browser updates.

Recommended fix High confidence

Chrome 99.0.4844.51 or later (stable channel)

  1. 1. Verify current Chrome version by navigating to chrome://settings/help
  2. 2. Download the latest stable Chrome installer from the official Google Chrome website (chrome.com)
  3. 3. Run the installer to update Chrome to version 99.0.4844.51 or later
  4. 4. Verify the update was successful by checking chrome://settings/help shows version 99.0.4844.51 or higher
  5. 5. Restart Chrome if prompted to complete the update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0799 — 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-0799 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