dbcve.org
ChromeWeb browser · Google

CVE-2022-0798

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
Use after free in MediaStream in Google Chrome prior to 99.0.4844.51 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension.

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

A use-after-free vulnerability exists in the MediaStream component of Google Chrome versions prior to 99.0.4844.51. The flaw can be triggered when a user installs a malicious Chrome extension, allowing the attacker to potentially exploit heap corruption through the freed memory location.

MitigationUpdate Chrome to version 99.0.4844.51 or later and remove any malicious or untrusted extensions from affected browsers.

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 installed Chrome version
    Navigate to chrome://settings/help or look at 'About Google Chrome' in the Chrome menu to see the current version number
    Affected if Version number is less than 99.0.4844.51 (e.g., 98.x, 97.x, etc.)
  2. Review installed extensions
    Navigate to chrome://extensions/ and inspect all enabled extensions. Look for unknown, untrusted, or recently added extensions you did not intentionally install
    Affected if Any extension is present that you do not recognize, trust, or intentionally added
  3. Check for suspicious extension permissions
    In chrome://extensions/, click 'Details' on each extension and review permissions. Look for permissions accessing MediaStream, webcam, microphone, or tabs/history beyond what seems necessary
    Affected if An extension has excessive or unnecessary permissions related to media capture or browsing activity
  4. Verify MediaStream usage
    When the vulnerable MediaStream component is in use (e.g., during a video call or when an extension accesses camera/microphone), check if the browser behaves unexpectedly or crashes
    Affected if Browser exhibits unusual behavior, crashes, or heap corruption symptoms during media capture operations with untrusted extensions enabled

You are affected if Chrome version is below 99.0.4844.51 AND you have untrusted or malicious extensions installed that could trigger the MediaStream use-after-free.

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

Update Chrome to version 99.0.4844.51 or later and remove any malicious or untrusted extensions from affected browsers.

Recommended fix High confidence

Chrome 99.0.4844.51 or later (any newer stable release)

  1. 1. Verify current Chrome version by navigating to chrome://settings/help
  2. 2. If the version is below 99.0.4844.51, proceed to update
  3. 3. Click 'Update Google Chrome' button if available and restart the browser
  4. 4. If no update button appears, download the latest stable Chrome from the official Google website (google.com/chrome)
  5. 5. Install the latest version and restart the browser
  6. 6. Verify the version now shows 99.0.4844.51 or later

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-0798 — 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-0798 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