Path Traversal
Also called directory traversal, LFI, RFI.
Using crafted paths to reach files outside the intended directory.
What it is
A vulnerability where unsanitized input containing directory sequences lets an attacker access files outside the intended folder. Related variants include local and remote file inclusion, which load attacker-referenced files.
Why it matters
Path traversal can disclose configuration files and secrets or, via inclusion variants, lead to code execution. It is a staple of web application testing and a common cause of sensitive-file exposure.
In practice
A download parameter set to a relative path with parent-directory sequences returns the server's password file instead of a report.
What to look for
- ../ sequences, encoded or doubled, in requests.
- Requests for files such as /etc/passwd or web.config.
- File name parameters passed straight to the file system.
Common mistake
Stripping ../ once. Encoded and nested sequences survive a single pass.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Command Injection: Injecting attacker commands into a shell call the app builds.
- Server-Side Request Forgery: Coercing a server into making attacker-chosen network requests.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.