fix(shared): reject insecure non-loopback gateway deep links#21970
Merged
fix(shared): reject insecure non-loopback gateway deep links#21970
Conversation
mbelinky
added a commit
that referenced
this pull request
Feb 20, 2026
f57fb0b to
b43f510
Compare
Contributor
|
Thanks for splitting this out and landing the deep-link/setup-code guardrails. This matches the intent of my earlier PR (#21268), and I like the move to strict loopback parsing plus the added tests. Happy to help test edge cases if you want another set of eyes One thought: should the user-facing error/message (or logs) include an actionable hint like “enable TLS / use a secure URL” to reduce support churn? |
b43f510 to
279173c
Compare
Contributor
Author
rodrigogs
pushed a commit
to rodrigogs/openclaw
that referenced
this pull request
Feb 20, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
Hansen1018
added a commit
to Hansen1018/openclaw
that referenced
this pull request
Feb 21, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
vincentkoc
pushed a commit
that referenced
this pull request
Feb 21, 2026
Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
dgarson
pushed a commit
to dgarson/clawdbot
that referenced
this pull request
Feb 21, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
mmyyfirstb
pushed a commit
to mmyyfirstb/openclaw
that referenced
this pull request
Feb 21, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
obviyus
pushed a commit
to guirguispierre/openclaw
that referenced
this pull request
Feb 22, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
mreedr
pushed a commit
to mreedr/openclaw-custom
that referenced
this pull request
Feb 24, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
6 tasks
hughdidit
pushed a commit
to hughdidit/DAISy-Agency
that referenced
this pull request
Mar 1, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky (cherry picked from commit ebae6f9)
hughdidit
pushed a commit
to hughdidit/DAISy-Agency
that referenced
this pull request
Mar 3, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky (cherry picked from commit ebae6f9) # Conflicts: # apps/shared/MoltbotKit/Tests/MoltbotKitTests/DeepLinksSecurityTests.swift
zooqueen
pushed a commit
to hanzoai/bot
that referenced
this pull request
Mar 6, 2026
…w#21970) Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 279173c Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- reject insecure non-loopback ws:// gateway deep links in shared parser\n- reject insecure non-loopback ws:// setup-code payload URLs\n- use strict loopback parsing (blocks 127.attacker.example bypass)\n- add shared DeepLinksSecurityTests and iOS parser coverage\n\n## Why\nThis lands the deep-link security intent from #21268 with a strict matcher and focused scope.
Greptile Summary
Adds security validation to reject insecure
ws://gateway deep links when connecting to non-loopback hosts. TheisLoopbackHosthelper uses Swift'sNetworkframework to parse and validate IPv4/IPv6 addresses, blocking prefix-bypass attacks like127.attacker.example. Validation is enforced in both the direct gateway deep link parser (DeepLinks.swift:170-172) and setup code payload parser (DeepLinks.swift:75-77).Confidence Score: 5/5
isLoopbackHostfunction correctly handles edge cases and bypass attempts.Last reviewed commit: f57fb0b