Auth Token Passed in GET URI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
During security assessment we found that 'When logged into the StackStorm WebUI, the user's auth token is passed in the URI of a number of GET requests to the API.
By including sensitive data, such as an auth token, in the URI of a GET request, there is an increased chance that the auth token's value is inadvertently disclosed and/or discovered by an attacker. The GET URI string will be stored in the web server's log files as well as those of HTTP proxies.
Proposed solution was to avoid sending the auth token in the URI of any GET requests, instead relying on headers to transmit authentication and authorization values for validation by the server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Trace the StackStorm WebUI's GET requests and API authentication handling, then verify that authentication tokens are sent through headers rather than GET URIs and are absent from request URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100