You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are evaluating CSET deployment in the enterprise configuration. We will have the frontend and backend on different servers. We've identified at least 26 instances in which the bearer token is passed via URL (e.g., search "?token="). Even with HTTPS enabled with CSET, this OWASP Number 1 and/or Number 2 vulnerability violates the very security standards implementations we want to document with CSET.
The text was updated successfully, but these errors were encountered:
faulkdev
changed the title
"A02_2021 Cryptographic_Failures" (i.e., #2 OWASP) in API URL token passing
JWT token in URL
Feb 18, 2025
We are evaluating CSET deployment in the enterprise configuration. We will have the frontend and backend on different servers. We've identified at least 26 instances in which the bearer token is passed via URL (e.g., search "?token="). Even with HTTPS enabled with CSET, this OWASP Number 1 and/or Number 2 vulnerability violates the very security standards implementations we want to document with CSET.
The text was updated successfully, but these errors were encountered: