dbcve.org
Omniverse LauncherApplication · Nvidia

CVE-2023-25524

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 1.8.11 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Omniverse Workstation Launcher for Windows and Linux contains a vulnerability in the authentication flow, where a user’s access token is displayed in the browser user's address bar. An attacker could use this token to impersonate the user to access launcher resources. A successful exploit of this vulnerability may lead to information disclosure.

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 · moderate confidence

NVIDIA Omniverse Workstation Launcher for Windows and Linux exposes user access tokens in the browser's address bar during the authentication flow. An attacker with access to browser history, network logs, or visual observation of the URL can capture these tokens and impersonate users to access launcher resources.

MitigationAvoid sharing screens during authentication and clear browser history/cache after login. Wait for NVIDIA's official patch to fix the token handling in the authentication flow.

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
Omniverse LauncherApplication
Affected:< 1.8.11

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Identify the installed NVIDIA Omniverse Launcher version
    Open the Omniverse Launcher, then access the application menu (usually top-left or via Help > About). Alternatively, check the installation directory for version metadata or run 'nvlnchr --version' if available in the command line.
    Affected if The displayed version is lower than 1.8.11 (e.g., 1.8.10, 1.8.0, etc.) or no version number is shown (unpatched installation).
  2. Review browser history for Omniverse URLs with tokens
    Open your browser's history/settings and search for URLs containing 'omniverse' or 'nvidia' that include query parameters with long alphanumeric strings (access tokens). In Chrome: chrome://history, in Firefox: about:history. Look for patterns like 'access_token=', 'token=', or 'auth=' in the URL.
    Affected if Browser history contains Omniverse Launcher authentication URLs with visible token strings in the address bar.
  3. Inspect saved credentials or autofill data
    Check browser password manager or system credential storage for any saved Omniverse entries. Also review browser autocomplete history for any cached Omniverse authentication URLs.
    Affected if Stored credentials or autocomplete entries contain URLs with exposed token parameters from the authentication flow.

You are affected if your NVIDIA Omniverse Launcher version is below 1.8.11 and you have performed authentication since the vulnerability was introduced, resulting in tokens visible in browser history or URL bar.

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 1.8.11 or later
Fixed in 1.8.11
Interim mitigation

Avoid sharing screens during authentication and clear browser history/cache after login. Wait for NVIDIA's official patch to fix the token handling in the authentication flow.

Recommended fix High confidence

Omniverse Launcher 1.8.11 or later

  1. Navigate to the official NVIDIA Omniverse download page or reference source at nvidia.custhelp.com
  2. Download Omniverse Launcher version 1.8.11 or later
  3. Uninstall the current vulnerable version of Omniverse Launcher if installed
  4. Install the downloaded updated version of Omniverse Launcher
  5. Verify the installation completed successfully and the version is 1.8.11 or higher
  6. Test the authentication flow to confirm the access token is no longer visible in the browser address bar

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Omniverse Launcher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25524 — 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-2023-25524 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