What problem does it solve? Security researchers need a disciplined, safe method to confirm path traversal vulnerabilities (CWE-22) without touching real secrets or system files, and to avoid filing reports that programs reject as expected behavior or out of scope. ## Core Features & Use Cases - Path Pipeline Mapping: Records the full chain from attacker-controlled input through decoding, joining, and canonicalization to the filesystem call for reads, writes, deletes, uploads, and archive extraction. - Concrete Test Recipes: Provides payload patterns for encoded traversal, nonstandard separators, storage-key injection, deep-link filenames, and post-validation mutation, all executed against disposable canary files. - Negative-Control Stop Conditions: Applies a 12-category taxonomy with real HackerOne report IDs to filter out non-reportable findings before submission. - Use Case: While testing a bug bounty target's /assets/<path> route, use this Skill to probe with ../outside.txt canaries, verify containment bypass, and check the version-boundary table to rule out already-patched libraries. ## Quick Start Ask the agent to hunt for path traversal in the target's file download and upload endpoints using canary files in a disposable test directory.
