dbcve.org
SidequestApplication · Sidequestvr

CVE-2024-21625

HIGH · 8.8 CVSS v3.1 Published 2024-01-04
Fix available
A fix is available. Upgrade to 0.10.35 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
SideQuest is a place to get virtual reality applications for Oculus Quest. The SideQuest desktop application uses deep links with a custom protocol (`sidequest://`) to trigger actions in the application from its web contents. Because, prior to version 0.10.35, the deep link URLs were not sanitized properly in all cases, a one-click remote code execution can be achieved in cases when a device is connected, the user is presented with a malicious link and clicks it from within the application. As of version 0.10.35, the custom protocol links within the electron application are now being parsed and sanitized properly.

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 confidence

SideQuest's Electron desktop application uses a custom protocol (`sidequest://`) for deep links to trigger actions from web content. Prior to version 0.10.35, deep link URLs were not properly sanitized, allowing one-click remote code execution when a user with a connected device clicks a malicious link within the application.

MitigationUpgrade SideQuest desktop application to version 0.10.35 or later, which properly parses and sanitizes custom protocol deep link URLs.

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
SidequestApplication
Affected:< 0.10.35

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed SideQuest version
    Open the SideQuest desktop application and navigate to the Help or About section to view the version number. Alternatively, if you can access the application's installation directory, check for version information in the app metadata or changelog file.
    Affected if version is displayed as below 0.10.35 or the version number is not visible (older unversioned builds)
  2. Compare version against affected range
    Verify that the installed version number falls below 0.10.35. Any version lower than 0.10.35 is in the affected range.
    Affected if installed version is less than 0.10.35
  3. Confirm custom protocol handler is registered
    Check if the sidequest:// custom protocol handler is registered on your system. On Windows, this may appear in registry keys under HKEY_CURRENT_USER\Software\Classes\sidequest or similar. On macOS, check if the application has registered itself as a handler for the sidequest:// protocol.
    Affected if sidequest:// protocol handler is registered and active on the system
  4. Verify deep link functionality is enabled
    Confirm that the application has network connectivity enabled and is configured to handle incoming deep link requests. This is typically the default behavior for the application.
    Affected if deep links can be processed by the application (default state when app is running)

You are affected if your SideQuest desktop application version is below 0.10.35 and the sidequest:// custom protocol handler is registered on your system, allowing the application to process deep link URLs.

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

Upgrade SideQuest desktop application to version 0.10.35 or later, which properly parses and sanitizes custom protocol deep link URLs.

Recommended fix High confidence

SideQuest version 0.10.35

  1. Check current SideQuest version by opening the application and navigating to Settings/About
  2. Download SideQuest version 0.10.35 or later from the official GitHub releases page at github.com
  3. Install the new version by running the downloaded installer
  4. Verify the installation was successful by checking the version in the application

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

Fix this in Sidequest Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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