From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Ganesh Jaybhay <ganesh(dot)jaybhay(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin][5919] Fix security related issues |
Date: | 2020-10-19 12:08:03 |
Message-ID: | CA+OCxowZ1XrTtZ2Caz0nRuNX5T8zQ3YbyJV5RDs80_v=f5m-Xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Mon, Oct 19, 2020 at 1:01 PM Ganesh Jaybhay <
ganesh(dot)jaybhay(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
>
> Please find the attached patch to fix the below security issues:
>
> - Host Header Injection - Added ALLOWED_HOSTS list to limit host
> address
> - Lack of Content Security Policy (CSP) - Added security header
> - Lack of Protection Mechanisms - HSTS - Added security header
> - Lack of Cookie Attribute – Secure : Kept as False as secure limits
> cookies to HTTPS traffic only.
> - Information Disclosure – Web Server / Development Framework
> VersionDescription: Kept as hard coded 'Python' instead of exposing
> wsgi/python/gunicorn version info.
>
> Please review and let me know if I have missed anything.
>
I took a very quick look at this, and one thing that immediately stood out
is that HSTS should definitely not be enabled by default. That can make
dev/test/redeploy extremely difficult.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
From | Date | Subject | |
---|---|---|---|
Next Message | Ganesh Jaybhay | 2020-10-19 13:46:58 | Re: [pgAdmin][5919] Fix security related issues |
Previous Message | Ganesh Jaybhay | 2020-10-19 12:01:07 | [pgAdmin][5919] Fix security related issues |