Individual skill

testing-for-regex-dos-redos

Testing web applications for Regular Expression Denial of Service (ReDoS), where crafted input forces a backtracking regex engine into super-linear (polynomial or exponential) processing time, hanging worker threads and causing denial of service. Also covers blind regex injection for char-by-char secret exfiltration when the attacker controls the pattern. Activates when input is matched against complex validators or when stored regex rules are attacker-influenced.

internal/tools/skills/data/web-application-security/testing-for-regex-dos-redos/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,310
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Testing for Regex Denial of Service (ReDoS)

## When to Use

- During authorized assessments of endpoints that validate input with regexes (email, URL, username, phone, "sanitizers")
- When the application reflects processing time or has visible per-request latency you can measure
- When stored rules, search patterns, or filters let an attacker supply or influence the regex itself (blind regex injection)
- When reviewing source/config and you can read the actual patterns in use
- When testing JS (browser/Node `RegExp`), Python `re`, Java `java.util.regex`, or PCRE — all backtracking engines

## Prerequisites

- **Authorization**: ReDoS is a DoS technique; confirm the scope explicitly allows latency/availability testing, ideally against staging
- **Measurement tooling**: `curl -w`, Burp Suite timing, or a small script that doubles input length and records latency