dbcve.org
ChromeWeb browser · Google

CVE-2022-3197

HIGH · 8.8 CVSS v3.1 Published 2022-09-26
Fix available
A fix is available. Upgrade to 105.0.5195.125 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 PDF in Google Chrome prior to 105.0.5195.125 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: High)

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 Google Chrome's PDF rendering component prior to version 105.0.5195.125. The flaw allows a remote attacker to exploit heap corruption by tricking a user into opening a specially crafted malicious PDF file.

MitigationUpdate Google Chrome to version 105.0.5195.125 or later to patch the vulnerability. Users should avoid opening untrusted PDF files until the browser is updated.

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.125
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. Verify Google Chrome is installed
    Check for Chrome executable: on Windows check Program Files or AppData folders, on Linux check /usr/bin/google-chrome or similar paths, on macOS check /Applications/Google Chrome.app
    Affected if Google Chrome is present on the system
  2. Determine installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command line on Linux/macOS, or check registry on Windows
    Affected if Version number is visible and less than 105.0.5195.125
  3. Confirm Fedora 37 environment (if applicable)
    Run 'cat /etc/fedora-release' or 'cat /etc/redhat-release' to identify the Linux distribution version
    Affected if System runs Fedora version 37 regardless of Chrome version
  4. Verify PDF functionality is enabled
    Attempt to open a PDF file in Chrome, or check chrome://plugins to confirm PDF viewer plugin status
    Affected if PDF viewer is enabled and functional in the browser
  5. Check for recent PDF file access
    Review Chrome's download history or recent file access logs for any untrusted or suspicious PDF files that may have been opened
    Affected if User has opened or attempted to open a PDF file from an untrusted source

User is affected if Google Chrome version is below 105.0.5195.125 (or running Fedora 37 with Chrome) AND the browser has PDF functionality enabled and the user may have opened a malicious PDF file.

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.125 or later
Fixed in 105.0.5195.125
Interim mitigation

Update Google Chrome to version 105.0.5195.125 or later to patch the vulnerability. Users should avoid opening untrusted PDF files until the browser is updated.

Recommended fix High confidence

Chrome 105.0.5195.125 or later (stable channel)

  1. 1. Check current Google Chrome version by navigating to chrome://settings/help
  2. 2. If version is earlier than 105.0.5195.125, update Chrome: On desktop, click 'Update Google Chrome' and restart, or manually download the latest version from google.com/chrome
  3. 3. For Fedora 37 systems with system-installed Chrome, run: sudo dnf update google-chrome-stable
  4. 4. Verify the update was successful by checking chrome://settings/help shows version 105.0.5195.125 or later
  5. 5. Restart Chrome to ensure the fix is fully applied

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