Path traversal outside an allowed root
A controlled path escapes the intended filesystem or object-key boundary.
Candidate CWE: CWE-22
Test hypothesis#
Place a harmless canary outside the local permitted root. Compare a normal in-root request, one relevant traversal path to the canary, and a nonexistent control while preserving raw request bytes.
Evidence required#
The outside marker is read or a disposable outside output is created. Include server-resolved path, normalization order, required privileges, and effective boundary.
Rule out false positives#
A reflected path, client-normalized request, error exposing a filename, or an intentionally accessible directory is not proof of traversal.
Playbook and command references#
- Uploads, downloads, paths, archives, and XML — Follow a file through acceptance, storage, processing, publication, and retrieval while preserving ownership and path boundaries.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.