View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 707 | Composr | core | public | 2012-07-28 20:20 | 2014-11-24 22:43 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 707: Support security tokens on POST forms | ||||
| Description | A security tactic is to force time-limited security tokens for POST forms, so that CSRF attacks cannot be used to perform malicious website requests. Composr has referrer testing, but if the user has referrers disabled then their security will be diminished. Also, if a hacker somehow has access to another part of the domain the referrer check would pass. Security tokens should be optional, perhaps with a white-list of pages that don't have them. This is so people can make their own POSTed forms without having to be a PHP programmer. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 5 | ||||
| Sponsorship open | |||||
|
|
Implemented this, but not quite as described. The security tokens are simply the session IDs. This has the advantage of not breaking the back button as the token can be re-used, having a much simpler implementation (no new DB table, for example), and being more robust. If the session ID was stolen, it is a theoretically weaker solution, but stealing of session IDs is already a major risk in itself and something we specifically guard against. There is an option for configuring what pages to not use this with, in case external integrations are required that do not have access to the session ID. |
