supported versions of our database system, including 11.5, 10.10,
9.6.15, 9.5.19, and 9.4.24, as well as the third beta of PostgreSQL 12.
This release fixes two security issues in the PostgreSQL server, two
security issues found in one of the PostgreSQL Windows installers, and
over 40 bugs reported since the previous release.
Users should install these updates as soon as possible.
A Note on the PostgreSQL 12 Beta
================================
In the spirit of the open source PostgreSQL community, we strongly
encourage you to test the new features of PostgreSQL 12 in your database
systems to help us eliminate any bugs or other issues that may exist.
While we do not advise you to run PostgreSQL 12 Beta 3 in your
production environments, we encourage you to find ways to run your
typical application workloads against this beta release.
Your testing and feedback will help the community ensure that the
PostgreSQL 12 release upholds our standards of providing a stable,
reliable release of the world's most advanced open source relational
database.
Security Issues
===============
Two security vulnerabilities have been closed by this release:
* CVE-2019-10208: `TYPE` in `pg_temp` executes arbitrary SQL during
`SECURITY DEFINER` execution
Versions Affected: 9.4 - 11
Given a suitable `SECURITY DEFINER` function, an attacker can execute
arbitrary SQL under the identity of the function owner. An attack
requires `EXECUTE` permission on the function, which must itself contain
a function call having inexact argument type match. For example,
`length('foo'::varchar)` and `length('foo')` are inexact, while
`length('foo'::text)` is exact. As part of exploiting this
vulnerability, the attacker uses `CREATE DOMAIN` to create a type in a
`pg_temp` schema. The attack pattern and fix are similar to that for
CVE-2007-2138.
Writing `SECURITY DEFINER` functions continues to require following the
considerations noted in the documentation:
https://www.postgresql.org/docs/devel/sql-createfunction.html#SQL-CREATEFUNCTION-SECURITY
The PostgreSQL project thanks Tom Lane for reporting this problem.
* CVE-2019-10209: Memory disclosure in cross-type comparison for hashed
subplan
Versions Affected: 11
In a database containing hypothetical, user-defined hash equality operators, an attacker could read arbitrary bytes of server memory. For an attack to become possible, a superuser would need to create unusual operators. It is possible for operators not purpose-crafted for attack to have the properties that enable an attack, but we are not aware of specific examples.
The PostgreSQL project thanks Andreas Seltenreich for reporting this problem.
Release Notes [1]
* Added extra validation for SQLAllocHandle (SQL_HANDLE_DESC, ...)
* Added GCC __attribute__ for checking format string
* Added missing define SQL_CONVERT_GUID
* Fixed issue using heap after free in SQLConnect_internal
* Fixed issue with global mutex in SQLError, SQLGetDiagRec, and SQLGetDiagField
* Fixed SQLSetStmtAttr to cache the correct values for SQL_ATTR_ROW_ARRAY_SIZE and SQL_ATTR_ROW_BIND_TYPE
* Fixed format specifiers and some casts to fix trace output
* Fixed missing check for section in SQLGetPrivateProfileString
* Fixed non-void function needs to return a value
* Fixed issue in Mac Cocoa code
* Fixed iODBC apps/frameworks CFBundleGetInfoString attribute
* Fixes an issue where build fails on Alpine
* Fixed package versioning
* Fixed small memory leaks
[1] http://www.iodbc.org/dataspace/doc/iodbc/wiki/iodbcWiki/ChangeNotes#2019-07-23%20-%20iODBC%20Stable%20Version%203.52.13%20Released
Maintainer reset due to the extended timeout, as per policy.
Take maintainership.
7 ports are bumped.
PR: 239367
Approved by: waitman@waitman.net (maintainer's timeout; ~6months on a PR#235789 for the same port)
It fails to build with PostgreSQL 11:
pgut/pgut.c:389:47: error: too few arguments to function call, expected 4, have 3
return simple_prompt("Password: ", 100, false);
~~~~~~~~~~~~~ ^
/usr/local/include/postgresql/server/port.h:193:1: note: 'simple_prompt' declared here
extern void simple_prompt(const char *prompt, char *destination, size_t destlen,
^
1 error generated.
http://package18.nyi.freebsd.org/data/120amd64-default-PR239514/2019-07-29_20h41m52s/logs/pg_reorg-1.1.11_2.log
And after fixing that one:
reorg.c:230:55: warning: incompatible pointer types passing 'bool [1]' to parameter of type 'const char *' [-Wincompatible-pointer-types]
execute_plan(SPI_OK_SELECT, plan_peek, values_peek, nulls_peek);
^~~~~~~~~~
./pgut/pgut-spi.h:28:84: note: passing argument to parameter 'nulls' here
extern void execute_plan(int expected, SPIPlanPtr plan, Datum *values, const char *nulls);
^
reorg.c:256:58: warning: incompatible pointer types passing 'bool *' to parameter of type 'const char *' [-Wincompatible-pointer-types]
execute_plan(SPI_OK_INSERT, plan_insert, &values[2], &nulls[2]);
^~~~~~~~~
[...]
reorg.c:573:34: error: use of undeclared identifier 'BTREE_AM_OID'
opclass = OpclassnameGetOpcid(BTREE_AM_OID, opcname);
^
reorg.c:590:57: error: member reference type 'FormData_pg_attribute' (aka 'struct FormData_pg_attribute') is not a pointer; did you mean to use '.'?
opcintype = RelationGetDescr(indexRel)->attrs[nattr]->atttypid;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
etc.
PR: 239514
This fixes the build with newer PostgreSQL versions.
Drop the IDXPATCH option. The patch no longer applies. Unfortunately
it was never upstreamed, its purpose is not clear, and the port no
longer has a maintainer to ask about this.
Changes: https://github.com/RhodiumToad/ip4r/blob/2.4.1/README.ip4r
PR: 239514
table_log.c:76:29: error: member reference type 'FormData_pg_attribute' (aka 'struct FormData_pg_attribute') is not a pointer; did you mean to use '.'?
if (!tupleDesc->attrs[i]->attisdropped) {
~~~~~~~~~~~~~~~~~~~^~
.
table_log.c:303:59: error: member reference type 'FormData_pg_attribute' (aka 'struct FormData_pg_attribute') is not a pointer; did you mean to use '.'?
if (trigdata->tg_relation->rd_att->attrs[col_nr - 1]->attisdropped) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
.
table_log.c:348:59: error: member reference type 'FormData_pg_attribute' (aka 'struct FormData_pg_attribute') is not a pointer; did you mean to use '.'?
if (trigdata->tg_relation->rd_att->attrs[col_nr - 1]->attisdropped) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
.
table_log.c:375:59: error: member reference type 'FormData_pg_attribute' (aka 'struct FormData_pg_attribute') is not a pointer; did you mean to use '.'?
if (trigdata->tg_relation->rd_att->attrs[col_nr - 1]->attisdropped) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
.
4 errors generated.
http://package18.nyi.freebsd.org/data/120amd64-default-PR239514/2019-07-29_20h41m52s/logs/tablelog-0.4.4_3.log
While here
- Mark it as deprecated. The last release was in 2007 and upstream
has been inactive since then.
- Fix WWW
PR: 239514
Reported by: antoine (via exp-run)
Sunpoet Po-Chuan Hsieh
Matthew Seaman
Thomas Zander
Palle Girgensohn
Tobias C. Berner
Tobias Kortkamp
Xin LI
Mahdi Mokhtari
Jason Helfman
Rene Ladan
Yuri Victorovich
Antoine Brodin
Kevin Bowling
Torsten Zuehlsdorff
Muhammad Moinur Rahman
Jan Beich
Bernard Spil