From owner-svn-ports-head@freebsd.org  Thu Aug  8 15:29:39 2019
Return-Path: <owner-svn-ports-head@freebsd.org>
Delivered-To: svn-ports-head@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 99285A96E2;
 Thu,  8 Aug 2019 15:29:39 +0000 (UTC)
 (envelope-from girgen@FreeBSD.org)
Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org
 [IPv6:2610:1c1:1:606c::19:3])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "mxrelay.nyi.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 464C3R3Yryz4SGN;
 Thu,  8 Aug 2019 15:29:39 +0000 (UTC)
 (envelope-from girgen@FreeBSD.org)
Received: from repo.freebsd.org (repo.freebsd.org
 [IPv6:2610:1c1:1:6068::e6a:0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5C08D272B5;
 Thu,  8 Aug 2019 15:29:39 +0000 (UTC)
 (envelope-from girgen@FreeBSD.org)
Received: from repo.freebsd.org ([127.0.1.37])
 by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x78FTdKS001479;
 Thu, 8 Aug 2019 15:29:39 GMT (envelope-from girgen@FreeBSD.org)
Received: (from girgen@localhost)
 by repo.freebsd.org (8.15.2/8.15.2/Submit) id x78FTdwt001478;
 Thu, 8 Aug 2019 15:29:39 GMT (envelope-from girgen@FreeBSD.org)
Message-Id: <201908081529.x78FTdwt001478@repo.freebsd.org>
X-Authentication-Warning: repo.freebsd.org: girgen set sender to
 girgen@FreeBSD.org using -f
From: Palle Girgensohn <girgen@FreeBSD.org>
Date: Thu, 8 Aug 2019 15:29:39 +0000 (UTC)
To: ports-committers@freebsd.org, svn-ports-all@freebsd.org,
 svn-ports-head@freebsd.org
Subject: svn commit: r508389 - head/security/vuxml
X-SVN-Group: ports-head
X-SVN-Commit-Author: girgen
X-SVN-Commit-Paths: head/security/vuxml
X-SVN-Commit-Revision: 508389
X-SVN-Commit-Repository: ports
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-ports-head@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SVN commit messages for the ports tree for head
 <svn-ports-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-ports-head>, 
 <mailto:svn-ports-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-head/>
List-Post: <mailto:svn-ports-head@freebsd.org>
List-Help: <mailto:svn-ports-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-ports-head>,
 <mailto:svn-ports-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 15:29:39 -0000

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>