Repository navigation
fix(security): SSRF guard checks resolved addresses, pins connection (v0.12.194) - #46
Merged
Merged
Conversation
added 2 commits
October 22, 2026 14:20
…he connection Port of ClawRouter#506. isBlockedSsrfHost() checked the hostname as written, so public names resolving to private addresses (localtest.me, 127.0.0.1.nip.io, 169.254.169.254.nip.io) passed, and fetch() re-resolved the name to connect, leaving a DNS-rebinding window. Each hop now resolves the host, refuses if any address is blocked, and connects only to the vetted addresses. Behind an upstream proxy the request still goes through it.
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.
Port of BlockRunAI/ClawRouter#506 —
src/local-guard.tswas byte-identical, so the patched file is copied as-is; proxy.ts passesviaUpstreamProxy; tests ported.img2img
image/maskURL downloads: the SSRF guard checked only the literal hostname, so public names resolving to private addresses passed, andfetch()re-resolved to connect (DNS-rebinding window). Each hop now resolves, refuses if any address is blocked, and pins the connection to the vetted addresses (node:http(s)lookupoverride, no undici). Behind an upstream proxy the request still goes through it.Release bump to 0.12.194, which also ships the catalog changes merged since 0.12.193. No publish workflow in this repo —
npm publishis manual after merge.