[CKAN-Security] data modifications using GET
jd at openup.org.za
Fri Apr 20 14:31:43 UTC 2018
Thank you very much for the update.
On 20 April 2018 at 16:19, Adrià Mercader <adria.mercader at okfn.org> wrote:
> Hi JD,
> Just a quick note to say that we are planning on working on a patch for
> this next week and backports it to the next patch releases which should be
> out hopefully in a couple of weeks with 2.8.
> Btw 2.8 is not affected by this.
> Have a great weekend
> On 12 Apr 2018 10:32 pm, "JD Bothma" <jd at openup.org.za> wrote:
> On Thu, 12 Apr 2018, 22:23 Adrià Mercader, <adria.mercader at okfn.org>
>> Many thanks for the report JD,
>> We'll work out a plan to address this and patch it as soon as we can.
>> We'll keep you posted.
>> On Thu, 12 Apr 2018, 17:03 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 'https://data.vulekamali.gov.za/user/edit/jd?name=jd&
>>> password=&password1=&password2=&save=' -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
+27 (0)79 281 6737
+27 (0)21 671 6306
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Security