Hardcoded File Paths

Hardcoded File Paths

Overview of the Vulnerability

Sensitive data can be exposed when it is not behind an authorization barrier. When this information is exposed it can place the application at further risk of compromise. This application has hardcoded file paths which can be used by an attacker to request files from the underlying system via directory traversal and can lead to exposure of data such as file naming conventions, system admin users, and permissions on the system.

Business Impact

This vulnerability can lead to sensitive data through the attacker’s ability to manipulate the application through their access to the hardcoded file paths. These malicious actions could also result in reputational damage for the business through the impact to customers’ trust.

Steps to Reproduce

  1. Enable a HTTP interception proxy, such as Burp Suite or OWASP ZAP

  2. Use a browser to navigate to: {{URL}}

  3. Capture the request using the HTTP interception proxy

  4. Observe the hardcoded file path exposed in the request / source code:

{{screenshot}}

Proof of Concept (PoC)

The following screenshot shows the hardcoded file path:

{{screenshot}}

Recommendation(s)

t is recommended to not hardcode any file paths within the application. Sensitive data should be encrypted both when at rest and when in transit. All data that is processed, stored, and transmitted by the application should be classified by business need, regulatory and industry requirements, and appropriate privacy laws.

Additionally, it is best practice to not store sensitive data when it is no longer required, as data that is not retained cannot be accessed and used maliciously. All sensitive data should therefore be a part of a regularly reviewed maintenance cycle. This review cycle should include rotation of secrets.

For more information refer to the following guides relating to this vulnerability:

PreviousHardcoded Sensitive DataNextHardcoded OAuth Secret

Last updated