testing-for-open-redirect-vulnerabilities
FeaturedIdentify and test open redirect vulnerabilities in web applications by analyzing URL redirection parameters, bypass techniques, and exploitation chains for phishing and token theft.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- mukul975
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- Created
- 8 months ago
- Last Updated
- 2 months ago
- Language
- Python
- License
- Apache-2.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
open-redirect
Open redirect playbook. Use when URL parameters, form actions, or JavaScript sinks control navigation targets and may redirect users to attacker-controlled destinations.
hunt-open-redirect
Hunt Open Redirect — all types including low-impact, chained to OAuth token theft → ATO, phishing chains. URL parameter manipulation, JavaScript redirect, meta refresh, header injection. Use when hunting redirect bugs or building ATO chains.
defend-open-redirect
Defensive methodology for open redirect (CWE-601) abuse, where a link on a trusted domain sends the victim off-site via a redirect parameter, used to cloak phishing behind your brand (MITRE ATT&CK T1566.002, T1204.001) and to steal OAuth authorization codes and tokens through an attacker-controlled redirect_uri (T1528). Keys off web server, reverse-proxy, and WAF access logs (nginx, Apache, IIS), 30x responses with an off-domain Location header, IdP sign-in logs (Entra ID, Okta), and Defender for Office 365 UrlClickEvents. Gives the defender view, signal-carrying log fields, a redirect-endpoint hunt, and allowlist and token-leak hardening. Use when hardening a redirect, returnUrl, or next parameter, reviewing OAuth redirect_uri validation, hunting phishing links cloaked by your own domain, investigating an off-site Location header, or preventing code and token leakage via Referer.