News for hackers. Stuff that matters.
Re:PostgreSQL Schema Design by combatentropy on Sunday March 29, 2020 @09:25PM (#22724390)
Speaking of security and schemas, I just learned about a vulnerability having to do with Postgres's public schema (CVE-2018-1058). It's possible only if you have untrusted users who can create objects, like tables and functions --- which is rare. As an example, someone could make a function in the public schema called "lower" which does something different than the function by the same name in pg_catalog (which lowercases strings). When other users call

  select lower(col) from table
they would be calling public.lower instead of pg_catalog.lower. This is just one example. They could do this for any commonly used function in pg_catalog.

The solution is one of:

   drop schema public;
   revoke create on schema public from public;
   alter role all set search_path = "$user";
That last one you could do in postgresql.conf instead.

--- https://www.postgresql.org/docs/current/ddl-schemas.html#DDL...

Re:PostgreSQL Schema Design by sbuttgereit on Sunday March 29, 2020 @09:51PM (#22724511)
Yep!

This is another reason why I don't favor actually using "public". Aside from issues like this it's in the default search_path and typically you want to leave it there. So when I do create other schemas, I also don't add them to the search_path globally or otherwise. Overall, I find the search_path setting spooky and, while it can save from typing, that saving ain't worth it... even setting it locally or for a session or a transaction... just no.