Non-Sensitive Token in URL

Sensitive data disclosure: Non-Sensitive Token in URL

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 discloses a non-sensitive token in the URL which an attacker can use to build word lists for brute-forcing valid tokens across the application environment.

Business Impact

When an application discloses a non-sensitive token in the URL it leaves the application more susceptible to future attacks.

Steps to Reproduce

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

2. Observe the exposed token in the URL

Proof of Concept (PoC)

The following screenshot shows the non-sensitive token in the URL:

{{screenshot}}

Recommendation(s)

The application should transmit tokens via HTTP cookies, or via hidden field forms which are submitted by using the HTTP Post method.

It is recommended to encrypt sensitive data 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 Open Web Application Security Project (OWASP) guide relating to this vulnerability: https://owasp.org/www-project-proactive-controls/v3/en/c8-protect-data-everywhere