Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by kccqzy on Thursday November 12, 2026 @05:10PM
(#50475045)
You can do authentication and authorization inside sql. For example you could have something like
And then you run SQL to validate any credentials and then check the database for any permissions, ending with
[ Parent
| on HN ]
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by mistrial9 on Thursday November 12, 2026 @05:39PM
(#50475421)
that requires additional privelages plus login.. I agree with the pp, sensationalism
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by NooneAtAll5 on Thursday November 12, 2026 @09:07PM
(#50477179)
who's pp?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by 14u2c on Thursday November 12, 2026 @10:32PM
(#50477880)
priginal poster.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by paustint on Thursday November 12, 2026 @11:30PM
(#50478348)
What's that?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by TeMPOraL on Friday November 13, 2026 @04:36AM
(#50480753)
It's like original o[y]ster, but with a shift left.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by somat on Thursday November 12, 2026 @08:48PM
(#50477054)
As an interesting thought experiment, if you do something like this and give your end users a full sql connection almost by definition you can't have a sql injection vulnerability, the database itself limits what access the clients have.
Now as to if this is actually a good idea and the database internal security is robust enough to handle full access, Well I have my doubts, It is a complicated poorly tested interface and results as disclosed by the article in question are probably not surprising.
I do run a toy application, where the experiment was to see if I could push all authentication and access control into the database, It is actually sort of neat not needing an auth layer in the application, but attacks like this were half expected.
see also: the schemaverse. A multiplayer space game where the game engine is postgres. https://github.com/Abstrct/Schemaverse
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by dprkh on Thursday November 12, 2026 @11:31PM
(#50478354)
Why use SQL for authentication and authorization? I understand that the point of SQL is so that the query optimizer can create an efficient execution plan, but there is no need for that when it comes to configuring auth, right?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by simcop2387 on Thursday November 12, 2026 @11:42PM
(#50478445)
It can severely simplify a lot of patterns like row level security and other things inside the database that need tigher access controls.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by jamesfinlayson on Friday November 13, 2026 @01:02AM
(#50478962)
I think at my day job it's used so that a bunch of things can connect to the production database to siphon off data for BI/do ancillary tasks (owned by other teams) without messing anything up, while the main business application that actually writes to the database has the ability to do pretty much everything.