detecting-logic-bypass
Detects logic bypass vulnerabilities including authentication bypass, authorization bypass, and business logic flaws. Use when analyzing authentication mechanisms, access controls, or investigating security control bypasses.
When & Why to Use This Skill
This Claude skill specializes in identifying logic bypass vulnerabilities, such as authentication and authorization flaws, within software applications. By automating the analysis of security controls and business logic, it helps developers and security teams proactively detect and mitigate risks like unauthorized access, privilege escalation, and business logic manipulation.
Use Cases
- Security Code Audits: Automatically identify missing authorization checks and insecure direct object references (IDOR) in complex codebases to prevent data leaks.
- Authentication Mechanism Analysis: Evaluate login flows and session management to detect vulnerabilities like weak password validation, session token exploitation, or timing attacks.
- Business Logic Validation: Trace transaction and state management logic to uncover flaws such as race conditions, state manipulation, or transaction abuse.
- Vulnerability Assessment & Reporting: Generate structured security reports with severity ratings, exploitability assessments, and actionable mitigation strategies for identified logic bypasses.
| name | detecting-logic-bypass |
|---|---|
| description | Detects logic bypass vulnerabilities including authentication bypass, authorization bypass, and business logic flaws. Use when analyzing authentication mechanisms, access controls, or investigating security control bypasses. |
Logic Bypass Detection
Detection Workflow
- Identify security controls: Find authentication mechanisms, authorization checks, validation functions, business logic rules
- Trace control flow: Use
xrefs_toto trace paths, identify bypass opportunities, check for missing checks - Check validation logic: Review validation functions, test bypass scenarios, assess validation completeness
- Assess bypass impact: What security control is bypassed? What's the business impact? How severe is the bypass?
Key Patterns
- Authentication bypass: weak password checks, session token weaknesses, timing attacks
- Authorization bypass: missing permission checks, insecure direct object references, privilege escalation
- Input validation bypass: blacklist-based validation, insufficient sanitization, regex bypass
- Business logic bypass: race conditions, state manipulation, transaction abuse
Output Format
Report with: id, type, subtype, severity, confidence, location, vulnerability, security control, bypass method, attack scenario, bypass steps, exploitability, impact, mitigation.
Severity Guidelines
- CRITICAL: Complete bypass of primary security control
- HIGH: Bypass of important security control
- MEDIUM: Partial bypass or edge case bypass
- LOW: Limited bypass with minor impact
See Also
patterns.md- Detailed detection patterns and exploitation scenariosexamples.md- Example analysis cases and code samplesreferences.md- CWE references and mitigation strategies