Logic Bypass Detection
Detection Workflow
- Identify security controls: Find authentication mechanisms, authorization checks, validation functions, business logic rules
- Trace control flow: Use
xrefs_to to 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 scenarios
examples.md - Example analysis cases and code samples
references.md - CWE references and mitigation strategies
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: detecting-logic-bypass3description: 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. Use when this capability is needed.4---56# Logic Bypass Detection78## Detection Workflow9101. **Identify security controls**: Find authentication mechanisms, authorization checks, validation functions, business logic rules112. **Trace control flow**: Use `xrefs_to` to trace paths, identify bypass opportunities, check for missing checks123. **Check validation logic**: Review validation functions, test bypass scenarios, assess validation completeness134. **Assess bypass impact**: What security control is bypassed? What's the business impact? How severe is the bypass?1415## Key Patterns1617- Authentication bypass: weak password checks, session token weaknesses, timing attacks18- Authorization bypass: missing permission checks, insecure direct object references, privilege escalation19- Input validation bypass: blacklist-based validation, insufficient sanitization, regex bypass20- Business logic bypass: race conditions, state manipulation, transaction abuse2122## Output Format2324Report with: id, type, subtype, severity, confidence, location, vulnerability, security control, bypass method, attack scenario, bypass steps, exploitability, impact, mitigation.2526## Severity Guidelines2728- **CRITICAL**: Complete bypass of primary security control29- **HIGH**: Bypass of important security control30- **MEDIUM**: Partial bypass or edge case bypass31- **LOW**: Limited bypass with minor impact3233## See Also3435- `patterns.md` - Detailed detection patterns and exploitation scenarios36- `examples.md` - Example analysis cases and code samples37- `references.md` - CWE references and mitigation strategies3839---40> Converted and distributed by [TomeVault](https://tomevault.io/claim/waiwai24) — claim your Tome and manage your conversions.41<!-- tomevault:4.0:skill_md:2026-04-13 -->