agentleFS
thejefflarsonthejefflarson/soundcheck/.claude/skills/open-redirect/SKILL.md

open-redirect

Skill20 starsChanged 4 months agoMITView on GitHub

Detects redirects to user-controlled URLs that enable phishing and OAuth

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ssti, xxe and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SubhiSecSkill

    ssti

    Hunt Server-Side Template Injection (SSTI) in Jinja2, Twig, Freemarker, Velocity, Smarty, ERB, Handlebars, Mustache, and Spring (SpEL). Use when input is reflected in a way that suggests template rendering — error pages, email templates, PDF generators, dynamic content systems.

    Also in 5 projects that use this

  • blacklanternsecuritySkill

    xxe

    Guide XML External Entity (XXE) injection exploitation during authorized penetration testing.

    Also in 4 projects that use this

  • SubhiSecSkill

    xss

    Hunt reflected, stored, and DOM-based Cross-Site Scripting (XSS) including CSP bypass, polyglot payloads, mutation XSS (mXSS), markdown XSS, and template XSS. Use when the user has identified a parameter or input that reflects to the page, or wants to test for XSS in a specific input.

    Also in 4 projects that use this

  • blacklanternsecuritySkill

    command-injection

    Guide OS command injection exploitation during authorized penetration testing.

    Also in 3 projects that use this

  • langbyyiSkill

    deserialization

    Insecure deserialization playbook. Use when Java, PHP, or Python applications deserialize untrusted data via ObjectInputStream, unserialize, pickle, or similar mechanisms that may lead to RCE, file access, or privilege escalation.

    Also in 3 projects that use this

  • +2 more from SubhiSec

The file

Files
SKILL.md

Open Redirect Security Check (CWE-601)

What this checks

Protects against open redirect vulnerabilities where an attacker crafts a link that redirects users from a trusted domain to a malicious site. Used in phishing campaigns to make malicious links appear legitimate, and in OAuth flows to steal authorization codes.

Vulnerable patterns

  • Redirect target read directly from a query parameter, form field, or request body and passed unchanged to the framework's redirect API.
  • Client-side navigation (window.location and equivalents) assigned a value derived from the URL or form input with no validation.
  • "Return to" or "next" parameters on login flows that accept any URL without an allowlist check.
  • Validation that uses prefix or substring matching against the allowed host — allowed.com.evil.com passes a naive prefix check.

Fix immediately

Flag the vulnerable code and explain the risk. Then suggest a fix that establishes these properties. Translate each property into the audited file's language and HTTP framework — use that framework's documented URL-parsing and redirect APIs.

  1. Every redirect target is either a relative path or a member of an exact host allowlist. Parse the URL, inspect the host component, and reject anything outside the allowlist. Prefix matching is not sufficient.
  2. Scheme-relative URLs are blocked explicitly. A value starting with // parses as a protocol-relative URL and redirects to whatever host follows. Checking only for http:// and https:// misses this.
  3. OAuth and login "return-to" parameters go through the same validator as any other redirect target. These are the highest-value targets because they run in an authenticated context; a redirect here hands the attacker the post-login session or an authorization code.
  4. On validation failure, redirect to a safe default (home, dashboard) rather than echoing an error containing the malicious URL. Echoing it back gives attackers a reflected-XSS surface.

Verification

  • Every redirect target derived from user input is validated as either a relative path or a member of an explicit host allowlist
  • Scheme-relative URLs (starting with //) are blocked — not just absolute http:// and https:// URLs
  • OAuth and login "return_to" parameters are validated before redirect
  • Validation failure routes to a safe default target, not back to the attacker-supplied URL

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.