CVE-2021-1072
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 · uneditedNVIDIA GeForce Experience, all versions prior to 3.21, contains a vulnerability in GameStream (rxdiag.dll) where an arbitrary file deletion due to improper handling of log files may lead to denial of service.
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 confidenceNVIDIA GeForce Experience versions prior to 3.21 contain an arbitrary file deletion vulnerability in the GameStream component (rxdiag.dll) stemming from improper handling of log files. An attacker with local access could exploit this to delete arbitrary files, potentially causing denial of service by removing critical system or application files.
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< 3.21CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify NVIDIA GeForce Experience is installedCheck for the presence of NVIDIA GeForce Experience on the system. Common installation paths: C:\Program Files\NVIDIA Corporation\GeForce Experience\ or check Add/Remove Programs in Control Panel.Affected if GeForce Experience is installed on the system.
-
Determine installed GeForce Experience versionOpen the GeForce Experience application and navigate to the Settings or About section to view the version number. Alternatively, right-click the executable at C:\Program Files\NVIDIA Corporation\GeForce Experience\GeForceExperience.exe, select Properties, and check the Details tab for the File Version.Affected if The displayed version is any version number lower than 3.21.
-
Locate the vulnerable rxdiag.dll componentSearch for the file rxdiag.dll in the GeForce Experience installation directory, typically found in C:\Program Files\NVIDIA Corporation\GeForce Experience\ or subdirectories.Affected if The file rxdiag.dll exists in the GeForce Experience installation folder, indicating the GameStream component is present.
-
Confirm GameStream functionality is enabledLaunch GeForce Experience and check the Settings or Preferences menu for GameStream settings. GameStream is typically enabled by default when the application is running.Affected if GameStream is enabled or has been configured on the system.
The system is affected if NVIDIA GeForce Experience is installed with a version lower than 3.21 and the GameStream component (rxdiag.dll) is present and enabled.
Generated from the published advisory. Verify against your own configuration.
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 data3.21
Upgrade NVIDIA GeForce Experience to version 3.21 or later. In enterprise environments, use patch management tools to inventory affected systems and deploy the update.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-1072 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-1072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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