fix: add URL validation in run-transfer.mjs - #106
Merged
LauJoeYing merged 1 commit intoAug 6, 2026
Merged
Conversation
Automated security fix generated by OrbisAI Security
LauJoeYing
approved these changes
Aug 6, 2026
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
Fix high severity security issue in
showcase/compass-guarded-transfer/scripts/run-transfer.mjs.Vulnerability
V-002showcase/compass-guarded-transfer/scripts/run-transfer.mjs:35Description: The normalizeInput function validates some input fields but fails to properly validate the compassUrl parameter. While it checks that compassUrl starts with 'https://', it does not validate the URL format comprehensively or prevent SSRF (Server-Side Request Forgery) attacks. The function accepts any HTTPS URL and passes it directly to the verify() function at line 48, which makes an HTTP POST request to that URL. An attacker can provide a malicious URL pointing to internal services or cloud metadata endpoints.
Evidence
Exploitation scenario: An attacker provides a malicious compassUrl like 'https://169.254.169.254/latest/meta-data/' (AWS metadata endpoint) or 'https://localhost:8080/admin' (internal service).
Scanner confirmation: multi_agent_ai rule
V-002flagged this pattern.Threat Model Context
This is a local CLI tool - exploitation requires the attacker to control command-line arguments or input files.
Changes
showcase/compass-guarded-transfer/scripts/run-transfer.mjsBehavior Preservation
The change is scoped to 1 file on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.
Security Invariant
Regression test
This test guards against regressions — it's useful independent of the code change above.
Automated security fix by OrbisAI Security