Geforce ExperienceApplication · Nvidia

CVE-2021-1079

MEDIUM · 6.1 CVSS v3.1 Published 2021-04-20
Fix available
A fix is available. Upgrade to 3.22 or later.
See remediation →
63/100
Remediation priority · Elevated
Zero-click

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
NVIDIA GeForce Experience, all versions prior to 3.22, contains a vulnerability in GameStream plugins where log files are created using NT/System level permissions, which may lead to code execution, denial of service, or local privilege escalation. The attacker does not have control over the consequence of a modification nor would they be able to leak information as a direct result of the overwrite.

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

NVIDIA GeForce Experience versions prior to 3.22 have a vulnerability in GameStream plugins where log files are created with NT/System-level permissions. This improper permission assignment allows local attackers to potentially achieve code execution, denial of service, or privilege escalation by interacting with these elevated-permission log files.

MitigationUpgrade NVIDIA GeForce Experience to version 3.22 or later to patch the vulnerable GameStream plugin log file permission handling.

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
Geforce ExperienceApplication
Affected:< 3.22

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 NVIDIA GeForce Experience is installed
    Look for the GeForce Experience installation in the system (typically in Program Files). The main executable is nvidia geforce experience.exe or similar NVIDIA software
    Affected if The software is present on the system and has a version number below 3.22
  2. Determine the installed version of GeForce Experience
    Open the GeForce Experience application and navigate to the About or Settings section to view the version number, or right-click the executable and view Properties > Details
    Affected if The installed version is lower than 3.22 (for example, 3.21, 3.20, etc.)
  3. Verify GameStream functionality is in use
    GameStream is a feature within GeForce Experience used for streaming games. Check if this feature has been configured or used on the system. Look for GameStream-related settings or logs within the GeForce Experience application
    Affected if GameStream has been enabled or used at least once on the system, creating log files in the application data or program data directories
  4. Inspect GameStream log file permissions
    Locate the log files created by the GameStream plugin (typically found in the GeForce Experience application data folder or GameStream logs directory). Right-click on these log files, go to Properties, and examine the Security tab to see which users or groups have access
    Affected if The log files are owned by SYSTEM or have NT Service permissions that grant elevated access beyond the standard user account, allowing potential privilege escalation

The system is affected if NVIDIA GeForce Experience version 3.22 or higher is not installed, and GameStream has been used, resulting in log files with elevated permissions.

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.

From vendor data
Upgrade available Upgrade to 3.22 or later
Fixed in 3.22
Interim mitigation

Upgrade NVIDIA GeForce Experience to version 3.22 or later to patch the vulnerable GameStream plugin log file permission handling.

Fix this in Geforce Experience 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-2021-1079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-1079 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