From owner-svn-ports-all@freebsd.org Thu Jun 27 21:05:56 2019 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53AAD15CE551; Thu, 27 Jun 2019 21:05:56 +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 ECBED715FA; Thu, 27 Jun 2019 21:05:55 +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 B88B71CD7A; Thu, 27 Jun 2019 21:05:55 +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 x5RL5tx1061562; Thu, 27 Jun 2019 21:05:55 GMT (envelope-from girgen@FreeBSD.org) Received: (from girgen@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x5RL5tA2061561; Thu, 27 Jun 2019 21:05:55 GMT (envelope-from girgen@FreeBSD.org) Message-Id: <201906272105.x5RL5tA2061561@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: girgen set sender to girgen@FreeBSD.org using -f From: Palle Girgensohn Date: Thu, 27 Jun 2019 21:05:55 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r505244 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: girgen X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 505244 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: ECBED715FA X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.95 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.95)[-0.948,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2019 21:05:56 -0000 Author: girgen Date: Thu Jun 27 21:05:55 2019 New Revision: 505244 URL: https://svnweb.freebsd.org/changeset/ports/505244 Log: Add vuxml entry for postgresql lt 10.9 and lt 11.4 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Jun 27 20:18:20 2019 (r505243) +++ head/security/vuxml/vuln.xml Thu Jun 27 21:05:55 2019 (r505244) @@ -58,6 +58,51 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + PostgreSQL -- Stack-based buffer overflow via setting a password + + + postgresql11-server + 11.4 + + + postgresql10-server + 10.9 + + + + +

The PostgreSQL project reports:

+
+

+ An authenticated user could create a stack-based buffer overflow + by changing their own password to a purpose-crafted value. In addition + to the ability to crash the PostgreSQL server, this could be further + exploited to execute arbitrary code as the PostgreSQL operating system account. +

+

+ Additionally, a rogue server could send a specifically crafted + message during the SCRAM authentication process and cause a libpq-enabled client + to either crash or execute arbitrary code as the client's operating system account. +

+

+ This issue is fixed by upgrading and restarting your PostgreSQL + server as well as your libpq installations. All users running + PostgreSQL 10, 11, and 12 beta are encouraged to upgrade as soon as possible. +

+
+ +
+ + https://www.postgresql.org/about/news/1949/ + CVE-2019-10164 + + + 2019-06-20 + 2019-06-27 + +
+ znc -- privilege escalation