I have run Zap scanning tool on my Grafana Project. we are using grafana 6.7.3 version.
Zap has reported Path Traversal Vulnerability alert of high severity. Below is detail of Alert -
| High (Medium) | Path Traversal |
|---|---|
| Description | The Path Traversal attack technique allows an attacker access to files, directories, and commands that potentially reside outside the web document root directory. An attacker may manipulate a URL in such a way that the web site will execute or reveal the contents of arbitrary files anywhere on the web server. Any device that exposes an HTTP-based interface is potentially vulnerable to Path Traversal. |
Most web sites restrict user access to a specific portion of the file-system, typically called the “web document root” or “CGI root” directory. These directories contain the files intended for user access and the executable necessary to drive web application functionality. To access files or execute commands anywhere on the file-system, Path Traversal attacks will utilize the ability of special-characters sequences.
The most basic Path Traversal attack uses the “…/” special-character sequence to alter the resource location requested in the URL. Although most popular web servers will prevent this technique from escaping the web document root, alternate encodings of the “…/” sequence may help bypass the security filters. These method variations include valid and invalid Unicode-encoding ("…%u2216" or “…%c0%af”) of the forward slash character, backslash characters ("…") on Windows-based servers, URL encoded characters “%2e%2e%2f”), and double URL encoding ("…%255c") of the backslash character.
Even if the web server properly restricts Path Traversal attempts in the URL path, a web application itself may still be vulnerable due to improper handling of user-supplied input. This is a common problem of web applications that use template mechanisms or load static text from files. In variations of the attack, the original URL parameter value is substituted with the file name of one of the web application’s dynamic scripts. Consequently, the results can reveal source code because the file is interpreted as text instead of an executable script. These techniques often employ additional special characters such as the dot (".") to reveal the listing of the current working directory, or “%00” NULL characters in order to bypass rudimentary file extension checks.|
||
|URL|http://<IpAddress>/api/admin/users|
|Method|POST|
|Parameter|login|
|Attack|\users|
|URL|http://<IpAddress>/api/admin/users|
|Method|POST|
|Parameter|login|
|Attack|/users|
|URL|http://<IpAddress>/api/admin/users|
|Method|POST|
|Parameter|login|
|Attack|users|
|Instances|3|
Could you please let me know the resolution for the vulnerability.
Regards,
Abhimanyu