CVE-2022-21817
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 Omniverse Launcher contains a Cross-Origin Resource Sharing (CORS) vulnerability which can allow an unprivileged remote attacker, if they can get user to browse malicious site, to acquire access tokens allowing them to access resources in other security domains, which may lead to code execution, escalation of privileges, and impact to confidentiality and integrity.
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 confidenceNVIDIA Omniverse Launcher has a CORS vulnerability that allows malicious cross-origin requests to acquire access tokens. An attacker can trick users into browsing a malicious site, which then makes requests to the Launcher to steal tokens and access resources across security domains, potentially leading to code execution and privilege escalation.
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< 1.5.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Omniverse Launcher version in Windows installed programsOpen Settings > Apps > Apps & features, or Control Panel > Programs and Features, and look for NVIDIA Omniverse Launcher in the list. Note the version number shown.Affected if The listed version is older than 1.5.2 (for example, 1.5.1, 1.5.0, or any version below 1.5.2)
-
Check version via Launcher application UIOpen the NVIDIA Omniverse Launcher application. Navigate to Help > About or the settings/preferences section where version information is typically displayed.Affected if The version displayed is below 1.5.2
-
Check installation directory for version filesNavigate to the default installation path (typically C:\Program Files\NVIDIA Omniverse Launcher or C:\Users\[User]\AppData\Local\Programs\omniverse-launcher) and look for version.info, version.txt, or similar files that may contain version metadata.Affected if The version file shows a build or version number lower than 1.5.2
You are affected if the installed NVIDIA Omniverse Launcher version is 1.5.1 or any version lower than 1.5.2.
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 · scoped1.5.2
Restrict Access-Control-Allow-Origin headers to trusted origins only and implement strict origin validation. Disable wildcard CORS policies and validate the Origin header server-side before issuing access tokens.
1.5.2 or later
- Download Omniverse Launcher version 1.5.2 or later from NVIDIA's official distribution渠道
- Install or update the Omniverse Launcher to version 1.5.2 or later
- Verify the installed version matches or exceeds 1.5.2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21817 — 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-21817 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