hunt-oauth

Identify OAuth vulnerabilities in web applications via HTTP responses and JavaScript.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Skobyn/talon --skill hunt-oauth-skobyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-oauth
Source: https://github.com/Skobyn/talon/tree/main/skills/hunt-oauth
Command: npx skills add https://github.com/Skobyn/talon --skill hunt-oauth-skobyn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit assists in discovering OAuth vulnerabilities, providing a systematic approach to hunting for and mitigating risks associated with OAuth implementations.

Core Features & Use Cases

  • OAuth Vulnerability Hunting: Specialized in identifying common OAuth vulnerabilities such as redirect_uri bypass, state parameter issues, and token theft.
  • Step-by-Step Methodology: Offers a detailed methodology for hunting OAuth vulnerabilities, including enumeration, mapping the OAuth flow, and testing various parameters.
  • Real Impact Examples: Includes real-world examples of OAuth vulnerabilities and their potential impact, providing context and severity.

Quick Start

Utilize the hunt-oauth skill to start hunting for OAuth vulnerabilities by running the 'enumerate-oauth-entry-points' command.

Frequently Asked Questions about hunt-oauth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the most common OAuth vulnerabilities to test for in web applications?

Common OAuth vulnerabilities include weak redirect_uri validation bypass, state parameter issues, and token theft. Identifying these flaws requires analyzing HTTP responses, JavaScript code, and server configurations during a security audit.

How do I find and test OAuth entry points during a penetration test?

To find OAuth entry points, start by running the enumerate-oauth-entry-points command. This maps the OAuth flow systematically, allowing you to test various parameters and hunt for vulnerabilities like redirect_uri bypass and state parameter issues.

How does a weak redirect_uri validation lead to OAuth token theft?

Weak redirect_uri validation allows attackers to manipulate the callback endpoint, intercepting authorization codes or access tokens. This OAuth token theft occurs when server configurations fail to strictly whitelist approved redirect URIs.

What is the best way to audit OAuth state parameter implementations for security flaws?

The best way to audit OAuth state parameter implementations is to check if the parameter is missing, predictable, or improperly validated. This vulnerability hunting step prevents cross-site request forgery attacks during the OAuth flow.

Can I use this methodology to test custom OAuth server configurations?

Yes, this vulnerability hunting methodology applies to custom OAuth server configurations. It provides a step-by-step approach to analyzing HTTP responses and JavaScript code to uncover implementation flaws.

Why does my OAuth flow fail during a security audit when testing redirect_uri bypasses?

OAuth flows may fail during redirect_uri bypass testing if the server configuration strictly validates URIs or blocks mismatched requests. Limitations arise when robust server-side whitelisting prevents token theft and redirect manipulation.