security-review-owasp-oauth

Review OAuth flows for account takeover and trust-boundary weaknesses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers find OAuth design and implementation flaws that can lead to account takeover, identity confusion, privilege escalation, or broken trust propagation.

Core Features & Use Cases

  • Reviews login, recovery, step-up, and session-adjacent OAuth flows for weak identity proof and unsafe fallback paths.
  • Checks how identity and authorization context moves across services, background jobs, and delegated actions.
  • Supports code, configuration, tests, documentation, and operational controls with evidence-based findings rather than generic advice.

Quick Start

Use the security-review-owasp-oauth skill to review the attached OAuth flow and call out confirmed weaknesses in identity proof, recovery, trust propagation, and privilege enforcement.

Frequently Asked Questions about security-review-owasp-oauth

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

FAQPage Schema
How do I review OAuth flows for account takeover risks?

OAuth account takeover occurs when weak identity proof or unsafe fallback paths in login and recovery flows allow attackers to hijack user accounts. Reviewing these flows involves tracing credential handling and privilege decisions against OWASP guidance to confirm safe failure handling.

How does OAuth identity propagation work across service-to-service calls?

OAuth identity propagation transfers authorization context across services and background jobs. Secure propagation requires tracing identity proof and privilege decisions across trust boundaries to prevent identity confusion or privilege escalation during delegated actions.

What is a trust boundary confusion vulnerability in OAuth?

Trust boundary confusion in OAuth occurs when identity and authorization context moves across services without proper validation, leading to identity confusion. Evidence-based tracing of privilege decisions and safe failure handling confirms whether trust propagation remains intact.

Does this OAuth security review cover step-up authorization flows?

Yes, the OAuth security review covers step-up authorization flows. It evaluates identity proof, privilege enforcement, and safe failure handling within these flows to prevent privilege escalation and account takeover based on OWASP guidance.

How to check OAuth configuration for weak recovery and delegation paths?

Check OAuth configuration for weak recovery and delegation paths by tracing identity proof and credential handling through evidence-based findings. Review operational controls, logging, and rate limiting to ensure safe failure handling against OWASP standards.

What are the limitations of generic OAuth security reviews?

Generic OAuth security reviews often lack evidence-based findings and fail to trace identity proof across trust boundaries. A targeted OWASP review provides concrete tracing of credential handling, privilege decisions, and rate limiting rather than generic advice.