dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 20 Apr 2023.
ChromeWeb browser · Google

CVE-2022-3038

HIGH · 8.8 CVSS v3.1 Published 2022-09-26
Fix available
A fix is available. Upgrade to 105.0.5195.52 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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 Network Service in Google Chrome prior to 105.0.5195.52 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

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 Google Chrome's Network Service component allows a remote attacker to exploit heap corruption via a crafted HTML page. The flaw exists in versions prior to 105.0.5195.52 and enables potential code execution through memory corruption.

MitigationUpdate Google Chrome to version 105.0.5195.52 or later to remediate this vulnerability.

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:< 105.0.5195.52
FedoraOperating system
Affected:= 37

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. Determine installed Google Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' or 'chromium-browser --version' from command line
    Affected if Version number is less than 105.0.5195.52 (e.g., 104.x.x.x, 103.x.x.x, etc.)
  2. Check operating system version
    Run 'cat /etc/os-release' or 'hostnamectl' to identify the Linux distribution and version
    Affected if Running Fedoraproject Fedora version 37 specifically
  3. Verify Chrome is installed and used
    Check for Chrome binary existence at typical locations like /usr/bin/google-chrome or /usr/bin/chromium, or check installed packages via 'rpm -qa | grep -i chrome' or 'dpkg -l | grep -i chrome'
    Affected if Chrome or Chromium browser is installed on the system
  4. Confirm Network Service is engaged
    When Chrome is running, the Network Service process (network_service.exe on Windows, or network-process on Linux) handles network requests; this component is active during normal browser use
    Affected if Chrome browser is actively used or has been used, as the vulnerability triggers via crafted HTML pages

The environment is affected if Google Chrome version is below 105.0.5195.52, especially on Fedora 37 systems where this specific version is marked as affected.

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

Update Google Chrome to version 105.0.5195.52 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome version 105.0.5195.52 or later (current stable release)

  1. Check current Chrome version by navigating to chrome://version in the browser address bar
  2. If the version is earlier than 105.0.5195.52, update Chrome to the latest stable version
  3. On Fedora 37, run: sudo dnf update google-chrome-stable
  4. Alternatively, manually download the latest Chrome stable from https://www.google.com/chrome/
  5. After installation/update, fully close and restart Chrome browser
  6. Verify the fix by navigating to chrome://version and confirming version 105.0.5195.52 or later is installed
Caveat None expected - this is a security patch update; user data and settings should be preserved

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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