Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: CVE-2019-9193 about COPY FROM/TO PROGRAM
Date: 2019-03-30 21:16:08
Message-ID: 8059.1553980568@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> I've noticed this post being currently shared on social media:

> https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2019-9193-authenticated-arbitrary-command-execution-on-postgresql-9-3/

> The claim that COPY FROM PROGRAM warrants a CVE seems groundless
> because you need to be superuser in the first place to do that.

Yeah; this is supposing that there is a security boundary between
Postgres superusers and the OS account running the server, which
there is not. We could hardly have features like untrusted PLs
if we were trying to maintain such a boundary.

> I don't know if there are precedents of people claiming
> CVE entries on Postgres without seemingly reaching out to the
> community first. Should something be done proactively about
> that particular claim?

Well, it's odd, because somebody at trustwave (not the actual
author of this "research") did reach out to the pgsql-security
list, and we discussed with him that it wasn't a violation of
Postgres' security model, and he agreed. But then they've
posted this anyway. Left hand doesn't talk to right hand there,
apparently.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gmail 2019-03-30 23:03:28 Re: stale WAL files?
Previous Message Daniel Verite 2019-03-30 18:14:47 CVE-2019-9193 about COPY FROM/TO PROGRAM