[CKAN-Security] data modifications using GET
david.read at hackneyworkshop.com
Thu Apr 12 17:41:28 UTC 2018
So a CSRF risk - dupe someone to click on one of these links and you
could change the user's email address to yours, do a password reset
and you control the user account.
Agreed, that's bad. Is there anything else to it I've missed?
On 12 April 2018 at 16:31, Ian Ward <ian at excess.org> wrote:
> Yes, this one is very bad. There is some checking for POST in the
> package controller but it seems like almost every method does it
> differently.. We'll have to audit them all.
> On Thu, Apr 12, 2018 at 10:57 AM, JD Bothma <jd at openup.org.za> wrote:
>> Hi there
>> Isn't it a serious security issue to allow data modification via GET
>> e.g. curl -v
>> -H 'cookie:...' ...
>> This changed my display name. Haven't checked if you can modify datasets
>> this way.
>> Further, since GET is whitelisted this CSRF protection isn't effective
>> Do you know of a way to stop modifications with GET other than modifying the
>> controllers? It looks like the same controllers are used for GET and POST
>> which means we can't just add method conditions in routing.py
>> CKAN security
>> Repo: https://github.com/ckan/ckan-security
> CKAN security
> Repo: https://github.com/ckan/ckan-security
More information about the Security