Executive summaryThe application allows log file access via the logname parameter in /tool/dynamicDialog.php, but lacks proper validation. This enables Path Traversal (e.g., ../), allowing attackers to access files outside the intended directory. The only restriction is the .log extension, making filesystem traversal possible.
Description
The application exposes a feature that allows viewing log files via the logname parameter of the /tool/dynamicDialog.php endpoint.
The controls applied to this parameter are insufficient and do not prevent Path Traversal sequences (e.g., ../). As a result, an attacker can manipulate this parameter to access files located outside the originally intended directory.
Analysis shows that the only effective constraint appears to be related to the file extension (.log), without strict path validation, allowing traversal of the filesystem hierarchy.
Attack Vectors
Network access: Remote
Authentication required: Low
User interaction: None required
Affected parameter: File Path
Triggered by injecting traversal sequences (../, %2e%2e%2f, %252e%252e%252f) into the parameter
Steps to Reproduce (PoC)
A crafted HTTP request can exploit this vulnerability by injecting directory traversal sequences: