A serious PostgreSQL security fix
Posted Apr 7, 2013 12:53 UTC (Sun) by gdt (subscriber, #6284)
Posted Apr 7, 2013 13:59 UTC (Sun) by cesarb (subscriber, #6266)
The bug in question involved the client sending an invalid database name.
Posted Apr 7, 2013 22:40 UTC (Sun) by hummassa (subscriber, #307)
Posted Apr 8, 2013 12:44 UTC (Mon) by tialaramex (subscriber, #21167)
So very likely you can connect to any TLS-supporting PostgreSQL server with proof that you're "A Badman <email@example.com>" and the server will go try to access the database to determine whether this "A Badman" person is authorized. With this particular bug, that's already too late.
In principle the server _could_ round up all the rules for authorization for all the databases, and then do early reject for connections that don't match, but that would be a lot of extra work to handle a slow path case, and (unless you know about this bug) there's no reason to approach it that way.
Posted Apr 7, 2013 23:31 UTC (Sun) by dlang (subscriber, #313)
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds