From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jacob Champion <pchampion(at)vmware(dot)com>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Post-CVE Wishlist |
Date: | 2021-11-24 19:57:15 |
Message-ID: | CA+TgmoZcqSnvxNujwGeNNn0azfVF=ui3P0k-Mum3yJaiXYKvHA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 24, 2021 at 2:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> One other point to be made here is that it seems like a stretch to call
> these particular bugs "high-severity".
Well, I was referring to the CVSS score, which was in the "high" range.
> Given what we learned about
> the difficulty of exploiting the libpq bug, and the certainty that any
> other clients sharing the issue would have their own idiosyncrasies
> necessitating a custom-designed attack, I rather doubt that we're going
> to hear of anybody trying to exploit the issue in the field.
I don't know. The main thing that I find consoling is the fact that
most people probably have the libpq connection behind a firewall where
nasty people can't even connect to the port. But there are probably
exceptions.
> (By no means do I suggest that these bugs aren't worth fixing when we
> find them. But so far they seem very easy to fix. So moving mountains
> to design out just this one type of bug doesn't seem like a great use
> of our finite earth-moving capacity.)
I have enough trouble just moving the couch.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2021-11-24 20:00:13 | Re: Post-CVE Wishlist |
Previous Message | Jacob Champion | 2021-11-24 19:56:54 | Re: Post-CVE Wishlist |