svn commit: r508389 - head/security/vuxml
Palle Girgensohn
girgen at FreeBSD.org
Thu Aug 8 15:29:39 UTC 2019
Author: girgen
Date: Thu Aug 8 15:29:38 2019
New Revision: 508389
URL: https://svnweb.freebsd.org/changeset/ports/508389
Log:
Add security information for PostgreSQL
Modified:
head/security/vuxml/vuln.xml
Modified: head/security/vuxml/vuln.xml
==============================================================================
--- head/security/vuxml/vuln.xml Thu Aug 8 15:28:13 2019 (r508388)
+++ head/security/vuxml/vuln.xml Thu Aug 8 15:29:38 2019 (r508389)
@@ -58,6 +58,80 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="9de4c1c1-b9ee-11e9-82aa-6cc21735f730">
+ <topic>PostgresSQL -- TYPE in pg_temp execute arbitrary SQL during `SECURITY DEFINER` execution</topic>
+ <affects>
+ <package>
+ <name>postgresql11-server</name>
+ <range><lt>11.5</lt></range>
+ </package>
+ <package>
+ <name>postgresql10-server</name>
+ <range><lt>10.10</lt></range>
+ </package>
+ <package>
+ <name>postgresql96-server</name>
+ <range><lt>9.6.15</lt></range>
+ </package>
+ <package>
+ <name>postgresql95-server</name>
+ <range><lt>9.5.19</lt></range>
+ </package>
+ <package>
+ <name>postgresql94-server</name>
+ <range><lt>9.4.24</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>The PostgreSQL project reports:</p>
+ <blockquote cite="https://www.postgresql.org/about/news/1960/">
+ <p>
+ Versions Affected: 9.4 - 11
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ Writing `SECURITY DEFINER` functions continues to require following
+ the considerations noted in the documentation:
+ </p>
+ <p>
+ https://www.postgresql.org/docs/devel/sql-createfunction.html#SQL-CREATEFUNCTION-SECURITY
+ </p>
+ </blockquote>
+ <blockquote cite="https://www.postgresql.org/about/news/1960/">
+ <p>
+ Versions Affected: 11
+ </p>
+ <p>
+ 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.
+ </p>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <url>https://www.postgresql.org/about/news/1960/</url>
+ <cvename>CVE-2019-10208</cvename>
+ <cvename>CVE-2019-10209</cvename>
+ </references>
+ <dates>
+ <discovery>2019-08-08</discovery>
+ <entry>2019-08-08</entry>
+ </dates>
+ </vuln>
+
<vuln vid="6e65dfea-b614-11e9-a3a2-1506e15611cc">
<topic>Django -- multiple vulnerabilities</topic>
<affects>
More information about the svn-ports-all
mailing list