If the back-end code takes that page parameter and plugs it directly into a file system call without checking it, an attacker can swap contact.html with our keyword string. The server might then attempt to "include" a sensitive system file, such as /etc/passwd , and display its contents to the attacker. The Risks of Improper File Handling A successful traversal attack can lead to:
Web applications often need to load dynamic content, such as images or localized text files. For example, a URL might look like this: https://example.com -include-..-2F..-2F..-2F..-2Froot-2F
: If an attacker can "include" a file they have previously uploaded (like a log file containing malicious scripts), they may execute code on the server. If the back-end code takes that page parameter
: This is the URL-encoded version of ../ . By repeating this sequence, the attacker moves up several levels. For example, a URL might look like this: https://example
Path traversal (also known as "dot-dot-slash" attacks) targets vulnerabilities in web applications that use user-supplied input to construct file paths. When an application doesn't properly sanitize this input, an attacker can use the ../ sequence to navigate upward through the server's file system. In the keyword provided:
: Attackers can read sensitive configuration files, database credentials, and system passwords.