Re:Dissecting PostgreSQL CVE-2013-1899
by agwa on Wednesday April 10, 2013 @07:58PM
(#5529052)
Nice article.
> Now we have to wait for an administrator to “su – postgres”. Likely? Eh.
This isn't that unlikely. On Debian/Ubuntu, postgres is the database super user and doesn't have a password set by default so the way to administer PostgreSQL is to su to postgres and then run psql/createdb/etc (it relies on local ident authentication).
Re:Dissecting PostgreSQL CVE-2013-1899
by ibotty on Thursday April 11, 2013 @09:58AM
(#5531967)
ehm. anti-virus? there's a whole discussion about it, i won't go into here.
but what can an anti-virus do? best would be to patch the database (might be pretty hard). then it could write something like:
echo "you have been hacked!"; exit 0
into the .profile. that will let the user spot the cracking attempt.
> Now we have to wait for an administrator to “su – postgres”. Likely? Eh.
This isn't that unlikely. On Debian/Ubuntu, postgres is the database super user and doesn't have a password set by default so the way to administer PostgreSQL is to su to postgres and then run psql/createdb/etc (it relies on local ident authentication).
Would be neat if there were an exploit which injected something to make further injection impossible.
but what can an anti-virus do? best would be to patch the database (might be pretty hard). then it could write something like: echo "you have been hacked!"; exit 0 into the .profile. that will let the user spot the cracking attempt.