In the pg_partman (aka PG Partition Manager) extension before 4.5.1 for PostgreSQL, arbitrary code execution can be achieved via SECURITY DEFINER functions because an explicit search_path is not set.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pg_partman | Pgxn | * | 4.5.1 (excluding) |
| Pg-partman | Ubuntu | bionic | * |
| Pg-partman | Ubuntu | focal | * |
| Pg-partman | Ubuntu | groovy | * |
| Pg-partman | Ubuntu | hirsute | * |
| Pg-partman | Ubuntu | impish | * |
| Pg-partman | Ubuntu | kinetic | * |
| Pg-partman | Ubuntu | trusty | * |
| Pg-partman | Ubuntu | upstream | * |
| Pg-partman | Ubuntu | xenial | * |
References
- https://github.com/pgpartman/pg_partman/commit/0b6565ad378c358f8a6cd1d48ddc482eb7f854d3
- https://github.com/pgpartman/pg_partman/compare/v4.5.0...v4.5.1
- https://security.netapp.com/advisory/ntap-20210625-0006/
- https://github.com/pgpartman/pg_partman/commit/0b6565ad378c358f8a6cd1d48ddc482eb7f854d3
- https://github.com/pgpartman/pg_partman/compare/v4.5.0...v4.5.1
- https://security.netapp.com/advisory/ntap-20210625-0006/