It has come to our attention that the PostGIS Raster support may give more privileges to users than an administrator is willing to grant. These include reading files from the filesystem and opening connections to network hosts.
Both issues can be limited in existing installations by setting the GDAL_SKIP variable (in the PostgreSQL server environment) to the list of all gdal drivers, but some drivers would still be forceably loaded by some operations.
Releases 2.1.3 and 2.0.6 strengthen the code to load no drivers by default and allows for a fine-grained tuning of what’s allowed and what not through postgis-specific environment variables:
Specifies a list of GDAL drivers to enable (rather than skip) By default all drivers are disabled. Example value: “GTiff PNG JPEG”
Enables read support for out-db raster bands if set to 1. By default out-db raster bands reading is disabled.
Upgrade is highly recommended, especially for online services allowing users to run arbitrary SQL queries.
Special thanks to Even Rouault for bringing up the issue and giving advice on its resolution.
The PostGIS Team is pleased to release PostGIS 3.0.3.
The PostGIS Team is pleased to release the third alpha of upcoming PostGIS 3.1.0 release. This version is exposes some of the new performance and feature enhancements in not yet relesed GEOS 3.9 as well as numerous speed enhancements not requiring newer GEOS. Requires GEOS 3.6+ and PostgreSQL 9.6+. To use MVT you will need protobuf-c 1.1. or higher.
Best served with
PostgreSQL 13.1, GEOS 3.7 or higher is recommended.
The PostGIS development team is pleased to provide bug fix and performance enhancements 3.0.2, 2.5.5, 2.4.9 for the 3.0, 2.5, and 2.4 stable branches.