silverstripe / silverstripe/developer-docs
Elaborate risks with disabling strict_user_agent_check
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 74
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 6
Description
Currently our docs have a Relaxing checks around user agent strings section
The warning about disabling the strict_user_agent_check should be further elaborate that why significantly increases the risk of session hijacking.
e.g.
When the strict_user_agent_check is disabled, the system no longer verifies that the user's browser (identified by its User-Agent string) matches the one stored in the session.
This significantly increases the risk of session hijacking, as an attacker who steals a session ID can use it to impersonate the user from a different browser or device.
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
Start with the “Relaxing checks around user agent strings” section linked in the issue. Expand the warning for disabling strict_user_agent_check to explain the browser mismatch check and the increased session-hijacking risk; it is done when those consequences are clear to readers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100