CVE-2022-42292
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 contains a vulnerability in the NVContainer component, where a user without administrator privileges can create a symbolic link to a file that requires elevated privileges to write to or modify, which may lead to denial of service, escalation of privilege or limited data tampering.
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 contains a vulnerability in the NVContainer component where an unprivileged user can create a symbolic link to a file that requires elevated privileges to write to or modify, potentially leading to denial of service, privilege escalation, or limited data tampering.
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.27.0.112CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify NVIDIA GeForce Experience is installedOpen Programs and Features (appwiz.cpl) or check C:\Program Files\NVIDIA Corporation\ for the GeForce Experience folder, or look for the NVIDIA GeForce Experience service in services.mscAffected if The software is not found in the system, the check does not apply
-
Determine installed GeForce Experience versionOpen the GeForce Experience application, go to About/Info section to view the version number, or right-click the executable in C:\Program Files\NVIDIA Corporation\GeForce Experience\ and view Properties > Details for the File VersionAffected if Version is present and is less than 3.27.0.112
-
Check NVContainer service statusOpen services.msc and look for services named NVContainer or similar NVIDIA container services, or check Task Manager for NVContainer.exe running processesAffected if NVContainer service or process is running or present on the system
-
Verify permissions on NVIDIA program directoriesUse icacls command on C:\Program Files\NVIDIA Corporation\ or specifically examine if standard users have Write or Create Symbolic Link permissions to directories used by NVContainerAffected if Standard (non-privileged) users have elevated write permissions that could allow symlink creation to privileged locations
If NVIDIA GeForce Experience version is installed and is less than 3.27.0.112 with the NVContainer component present and accessible to unprivileged users, the environment is affected by this vulnerability.
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.
dbcve · scoped3.27.0.112
Apply the latest NVIDIA GeForce Experience security update to remediate this vulnerability.
3.27.0.112 or later
- 1. Open NVIDIA GeForce Experience application
- 2. Navigate to Settings (gear icon)
- 3. Click on the 'About' or 'Updates' section
- 4. Check for updates and install the latest version
- 5. Alternatively, download the latest version from the official NVIDIA website: https://www.nvidia.com/en-us/geforce/geforce-experience/
- 6. Ensure the installed version is 3.27.0.112 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42292 — 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-2022-42292 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