Re: Compromised postgresql instances

2018-06-09 Thread Andrew Dunstan
On 06/09/2018 03:27 AM, Andrew Gierth wrote: "Thomas" == Thomas Kellerer writes: Thomas> And a blog post going into details on how that specific attack works. Thomas>

Re: Compromised postgresql instances

2018-06-09 Thread Andrew Gierth
> "Thomas" == Thomas Kellerer writes: Thomas> And a blog post going into details on how that specific attack works. Thomas> https://www.imperva.com/blog/2018/03/deep-dive-database-attacks-scarlett-johanssons-picture-used-for-crypto-mining-on-postgre-database/ *headdesk* *headdesk*

Re: Compromised postgresql instances

2018-06-08 Thread Thomas Kellerer
> Please cite actual instances of such reports. Vague queries like this help nobody. There were several questions on SO https://stackoverflow.com/questions/49815460 https://stackoverflow.com/questions/47499766 https://stackoverflow.com/questions/47741077

Re: Compromised postgresql instances

2018-06-08 Thread Andrew Dunstan
On 06/08/2018 06:13 PM, Andrew Gierth wrote: "Tom" == Tom Lane writes: > Andrew Dunstan writes: >> Please cite actual instances of such reports. Vague queries like >> this help nobody. We do also get them on the IRC channel every once in a while, not very frequently but enough to

Re: Compromised postgresql instances

2018-06-08 Thread Andrew Gierth
> "Tom" == Tom Lane writes: > Andrew Dunstan writes: >> Please cite actual instances of such reports. Vague queries like >> this help nobody. We do also get them on the IRC channel every once in a while, not very frequently but enough to notice (maybe 2-3 so far this year?). Tom>

Re: Compromised postgresql instances

2018-06-08 Thread Andrew Dunstan
On 06/08/2018 04:54 PM, Steve Atkins wrote: On Jun 8, 2018, at 1:47 PM, Tom Lane wrote: Andrew Dunstan writes: On 06/08/2018 04:34 PM, Steve Atkins wrote: I've noticed a steady trickle of reports of postgresql servers being compromised via being left available to the internet with

Re: Compromised postgresql instances

2018-06-08 Thread Steve Atkins
> On Jun 8, 2018, at 1:47 PM, Tom Lane wrote: > > Andrew Dunstan writes: >> On 06/08/2018 04:34 PM, Steve Atkins wrote: >>> I've noticed a steady trickle of reports of postgresql servers being >>> compromised via being left available to the internet with insecure or >>> default

Re: Compromised postgresql instances

2018-06-08 Thread Tom Lane
Andrew Dunstan writes: > On 06/08/2018 04:34 PM, Steve Atkins wrote: >> I've noticed a steady trickle of reports of postgresql servers being >> compromised via being left available to the internet with insecure or >> default configuration, or brute-forced credentials. The symptoms are >>

Re: Compromised postgresql instances

2018-06-08 Thread Andrew Dunstan
On 06/08/2018 04:34 PM, Steve Atkins wrote: I've noticed a steady trickle of reports of postgresql servers being compromised via being left available to the internet with insecure or default configuration, or brute-forced credentials. The symptoms are randomly named binaries being uploaded

Compromised postgresql instances

2018-06-08 Thread Steve Atkins
I've noticed a steady trickle of reports of postgresql servers being compromised via being left available to the internet with insecure or default configuration, or brute-forced credentials. The symptoms are randomly named binaries being uploaded to the data directory and executed with the