Skip to content

Security: replace credential-bearing custom pairing URLs with verified app links #17397

Closed

Description

@tekumara

Summary

Externally delivered pairing links use the custom orca:// URL scheme and contain bearer credentials. Another installed app can register the same scheme and receive the link instead of Orca.

Evidence

The encoded offer contains the desktop device token and, for Relay pairing, an invite credential valid for up to approximately 10 minutes.

Impact

A malicious installed app that claims the same scheme can intercept the offer and race the legitimate phone to authenticate or complete Relay pairing. Successful credential theft exposes the desktop RPC capabilities granted to a paired mobile device.

Suggested fix

Use verified HTTPS Universal Links on iOS and Android App Links with associated-domain verification. Keep the custom scheme only for navigation that carries no secret. Pairing values should also be short-lived and atomically single-use.

Activity

  1. AmethystLiang commented on Aug 30, 2026

    @AmethystLiang
    Contributor

    thanks for reporting. looking into it

  2. added theissue type on Sep 19, 2026
  3. nwparker commented on Oct 26, 2026

    @nwparker
    Contributor

    Fixed by #27475: pairing links are now verified https links, and the orca:// link no longer carries the credential. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions