CVE-2021-1073
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.23, contains a vulnerability in the login flow when a user tries to log in by using a browser, while, at the same time, any other web page is loaded in other tabs of the same browser. In this situation, the web page can get access to the token of the user login session, leading to the possibility that the user’s account is compromised. This may lead to the targeted user’s data being accessed, altered, or lost.
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 confidenceThis is a session token leakage vulnerability in the web-based login flow of NVIDIA GeForce Experience. When a user authenticates through a browser, the login session token is improperly exposed to other browser tabs sharing the same origin, allowing malicious pages to steal the session and compromise the user's account.
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.23CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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.
-
Check if NVIDIA GeForce Experience is installedOpen Windows Settings > Apps & Features (or Programs and Features in Control Panel) and search for 'NVIDIA GeForce Experience'. Alternatively, check for the installation folder at C:\Program Files\NVIDIA Corporation\GeForce Experience\ if it exists.Affected if The application is not found in the system, meaning it is not installed and not affected by this specific vulnerability.
-
Determine the installed version of GeForce ExperienceIf installed, locate the version by right-clicking the GeForce Experience executable (typically 'GeForceExperience.exe' in the installation folder), selecting Properties, and viewing the File Version on the Details tab. Or right-click the app in Apps & Features and select 'Advanced options' to view the Version.Affected if The version number displayed is lower than 3.23 (for example, 3.22.x, 3.21.x, or earlier). Any version below 3.23 is affected.
-
Verify the web-based login feature was usedOpen GeForce Experience and check if the user has previously logged in through the in-app browser (the login page that opens within the application using embedded browser functionality). This is distinct from the desktop login method.Affected if The user has authenticated using the browser-based login flow within GeForce Experience, as this is the only scenario where session token leakage to other browser tabs can occur.
-
Check for suspicious browser session activity (optional)Open the web browser that GeForce Experience uses for login (check browser history and cookies). Look for any unfamiliar active sessions or tokens that may have been imported. In Chrome, go to Settings > Advanced > Site Settings > Cookies and Site Data to view active sessions.Affected if Unexpected active sessions are found that correspond to NVIDIA services, suggesting potential token theft, though this step is for post-incident detection rather than vulnerability confirmation.
If NVIDIA GeForce Experience version 3.23 or later is confirmed to be installed, the environment is not affected by this session token leakage 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.
From vendor data3.23
Upgrade to NVIDIA GeForce Experience version 3.23 or later. As a workaround, avoid having other web pages open when logging in through the browser.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1073 — 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-1073 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