security-review-owasp-oauth2

Review OAuth 2 implementations for security weaknesses against OWASP guidance.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-oauth2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-oauth2
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-oauth2
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-oauth2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers find security weaknesses in OAuth 2 implementations before they become token theft, replay, or authorization-flow issues.

Core Features & Use Cases

  • Flow Review: Inspect authorization code, PKCE, redirect, state, and mix-up defenses across clients and authorization servers.
  • Token Protection Review: Evaluate access token, refresh token, audience, and replay-resistance controls for realistic abuse paths.
  • Client Authentication Review: Check confidential-client authentication and flag legacy or unsafe grant usage such as implicit or password flows.
  • Use Case: Review a sign-in integration to confirm that code exchange, redirect validation, and token handling align with OWASP OAuth 2 guidance.

Quick Start

Use the security-review-owasp-oauth2 skill to review the attached OAuth 2 implementation for authorization-code handling, redirect validation, token replay defenses, and client authentication issues.

Frequently Asked Questions about security-review-owasp-oauth2

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

FAQPage Schema
How do I review OAuth 2 authorization code flows for security weaknesses?

Review OAuth 2 authorization code flows by inspecting PKCE usage, redirect URI validation, and state parameter checks across clients and authorization servers. Evidence-based assessment confirms code exchange handling aligns with OWASP guidance.

What is the best way to prevent token replay attacks in OAuth 2 implementations?

Prevent token replay attacks in OAuth 2 by evaluating access token, refresh token, and audience controls using evidence-based assessment. Review replay-resistance protections in token lifecycle handling against realistic abuse paths.

When do I need PKCE validation in OAuth 2 redirect handling?

PKCE validation in OAuth 2 redirect handling is needed for authorization code flows to prevent interception attacks. Review PKCE implementation across clients and authorization servers to confirm proper code exchange and mix-up defenses.

Does this OAuth 2 review check for unsafe legacy grant types like implicit flow?

This OAuth 2 review checks confidential-client authentication and flags legacy or unsafe grant usage such as implicit or password flows. Evidence-based assessment identifies forbidden legacy flows against OWASP OAuth 2 guidance.

Can I review token lifecycle protections and refresh token handling for OAuth 2?

Review token lifecycle protections and refresh token handling for OAuth 2 by evaluating access token, refresh token, and audience controls. Evidence-based assessment identifies realistic abuse paths and replay-resistance gaps.

Why does OAuth 2 redirect URI validation fail during security review?

OAuth 2 redirect URI validation fails during security review when redirect handling lacks strict matching across clients and authorization servers. Evidence-based assessment checks redirect URI checks, state validation, and mix-up defenses against OWASP guidance.