Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JWT token in URL #4448

Open
faulkdev opened this issue Feb 18, 2025 · 0 comments
Open

JWT token in URL #4448

faulkdev opened this issue Feb 18, 2025 · 0 comments

Comments

@faulkdev
Copy link

faulkdev commented 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.

@faulkdev faulkdev changed the title "A02_2021 Cryptographic_Failures" (i.e., #2 OWASP) in API URL token passing JWT token in URL Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant