INJ-009medium SeverityInjection Sinks & Input Validation
No Regex Denial of Service (ReDoS) Vulnerabilities
Agents write complex nested regular expressions like /([a-z]+)+$/ for email or URL checks that hang on crafted input.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "No Regex Denial of Service (ReDoS) Vulnerabilities" (INJ-009). Issue: Agents write complex nested regular expressions like /([a-z]+)+$/ for email or URL checks that hang on crafted input. Remediation required: Use simple, well-tested regular expressions without catastrophic backtracking or use dedicated validation libraries. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
Agents write complex nested regular expressions like /([a-z]+)+$/ for email or URL checks that hang on crafted input.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: No Regex Denial of Service (ReDoS) Vulnerabilities
// Problematic pattern: Agents write complex nested regular expressions like /([a-z]+)+$/ for email or URL checks that hang on crafted input.Launch-Ready Fix
// Production-ready fix for: No Regex Denial of Service (ReDoS) Vulnerabilities
// Recommended remediation: Use simple, well-tested regular expressions without catastrophic backtracking or use dedicated validation libraries.Remediation & Verification Checklist
Remediation: Use simple, well-tested regular expressions without catastrophic backtracking or use dedicated validation libraries.
- Search your codebase for pattern matching "No Regex Denial of Service (ReDoS) Vulnerabilities".
- Apply the recommended remediation: Use simple, well-tested regular expressions without catastrophic backtracking or use dedicated validation libraries.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.