aboutsummaryrefslogtreecommitdiffstats
path: root/databases/postgresql95-pltcl
diff options
context:
space:
mode:
authorgirgen <girgen@FreeBSD.org>2019-08-08 23:33:02 +0800
committergirgen <girgen@FreeBSD.org>2019-08-08 23:33:02 +0800
commite0d9bc6b7619e4bb98beaf958e1d133c19503bcb (patch)
treefc0ee30cbf842c4eaf667353b27c72633e18ed48 /databases/postgresql95-pltcl
parent1896875b545da34ef7ebddfb011e4749b080a56d (diff)
downloadfreebsd-ports-gnome-e0d9bc6b7619e4bb98beaf958e1d133c19503bcb.tar.gz
freebsd-ports-gnome-e0d9bc6b7619e4bb98beaf958e1d133c19503bcb.tar.zst
freebsd-ports-gnome-e0d9bc6b7619e4bb98beaf958e1d133c19503bcb.zip
iThe PostgreSQL Global Development Group has released an update to all
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.
Diffstat (limited to 'databases/postgresql95-pltcl')
-rw-r--r--databases/postgresql95-pltcl/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/databases/postgresql95-pltcl/Makefile b/databases/postgresql95-pltcl/Makefile
index 709efefafab7..e673bb12af62 100644
--- a/databases/postgresql95-pltcl/Makefile
+++ b/databases/postgresql95-pltcl/Makefile
@@ -3,4 +3,4 @@
WANT_PGSQL_VER= 9.5
-.include "${.CURDIR}/../postgresql96-pltcl/Makefile"
+.include "${.CURDIR}/../postgresql12-pltcl/Makefile"