defend-open-redirectlisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Open Redirect - Defensive Methodology
> **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, the hunt, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet.
## TL;DR
An open redirect is an endpoint on your own domain that takes a destination from user input and sends the browser there without checking it. Attackers do not exploit it to break into your app; they use it so a phishing link reads as `https://trusted.example.com/login?returnUrl=https://evil.tld` and inherits your reputation, your TLS, and your email-gateway allowlisting. The same flaw in an OAuth or OIDC flow leaks authorization codes and access tokens when a loosely matched `redirect_uri` or a trailing open redirect bounces the credential to an attacker host. Fix it by never redirecting to a caller-supplied absolute URL: map an opaque key to a server-side destination, or enforce an exact-host allowlist after full canonicalization. Detect it by parsing redirect endpoints out of web and proxy logs and flagging off-domain targets.
## What it looks like, defender view
In telemetry this shows up as a request to one of your redirect endpoints carrying a target parameter that