From owner-svn-ports-all@freebsd.org Sat Jun 16 14:43:01 2018 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 5A83E10186B8; Sat, 16 Jun 2018 14:43:01 +0000 (UTC) (envelope-from jrm@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2720083C14; Sat, 16 Jun 2018 14:43:01 +0000 (UTC) (envelope-from jrm@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 098E327AF4; Sat, 16 Jun 2018 14:43:01 +0000 (UTC) (envelope-from jrm@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5GEh013002098; Sat, 16 Jun 2018 14:43:00 GMT (envelope-from jrm@FreeBSD.org) Received: (from jrm@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5GEh0TX002097; Sat, 16 Jun 2018 14:43:00 GMT (envelope-from jrm@FreeBSD.org) Message-Id: <201806161443.w5GEh0TX002097@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jrm set sender to jrm@FreeBSD.org using -f From: Joseph Mingrone Date: Sat, 16 Jun 2018 14:43:00 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r472550 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: jrm X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 472550 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 16 Jun 2018 14:43:01 -0000 Author: jrm Date: Sat Jun 16 14:43:00 2018 New Revision: 472550 URL: https://svnweb.freebsd.org/changeset/ports/472550 Log: security/vuxml: document Slurm vulnerability https://lists.schedmd.com/pipermail/slurm-announce/2018/000008.html While here, silence validation warnings caused by node.js 2018-06-15 entry. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Sat Jun 16 14:21:11 2018 (r472549) +++ head/security/vuxml/vuln.xml Sat Jun 16 14:43:00 2018 (r472550) @@ -58,6 +58,35 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + slurm -- insecure handling of user_name and gid fields + + + slurm-wlm + 17.02.11 + + + + +

SchedMD reports:

+
Insecure handling of user_name and gid fields (CVE-2018-10995)
+
While fixes are only available for the supported 17.02 and 17.11 + releases, it is believed that similar vulnerabilities do affect past + versions as well. The only resolution is to upgrade Slurm to a fixed + release.
+

+ + + + https://lists.schedmd.com/pipermail/slurm-announce/2018/000008.html + + + 2018-05-30 + 2018-06-16 + + + node.js -- multiple vulnerabilities @@ -78,43 +107,43 @@ Notes:

Node.js reports:

-
Denial of Service Vulnerability in HTTP/2 (CVE-2018-7161)
+
Denial of Service Vulnerability in HTTP/2 (CVE-2018-7161)

All versions of 8.x and later are vulnerable and the severity is - HIGH. An attacker can cause a denial of service (DoS) by causing a - node server providing an http2 server to crash. This can be - accomplished by interacting with the http2 server in a manner that - triggers a cleanup bug where objects are used in native code after - they are no longer available. This has been addressed by updating - the http2 implementation. Thanks to Jordan Zebor at F5 Networks for - reporting this issue.
-
Denial of Service, nghttp2 dependency (CVE-2018-1000168)
+ HIGH. An attacker can cause a denial of service (DoS) by causing a + node server providing an http2 server to crash. This can be + accomplished by interacting with the http2 server in a manner that + triggers a cleanup bug where objects are used in native code after + they are no longer available. This has been addressed by updating + the http2 implementation. Thanks to Jordan Zebor at F5 Networks for + reporting this issue.
+
Denial of Service, nghttp2 dependency (CVE-2018-1000168)

All versions of 9.x and later are vulnerable and the severity is - HIGH. Under certain conditions, a malicious client can trigger an - uninitialized read (and a subsequent segfault) by sending a - malformed ALTSVC frame. This has been addressed through an by - updating nghttp2.
-
Denial of Service Vulnerability in TLS (CVE-2018-7162)
+ HIGH. Under certain conditions, a malicious client can trigger an + uninitialized read (and a subsequent segfault) by sending a + malformed ALTSVC frame. This has been addressed through an by + updating nghttp2.
+
Denial of Service Vulnerability in TLS (CVE-2018-7162)

All versions of 9.x and later are vulnerable and the severity is - HIGH. An attacker can cause a denial of service (DoS) by causing a - node process which provides an http server supporting TLS server to - crash. This can be accomplished by sending duplicate/unexpected - messages during the handshake. This vulnerability has been addressed - by updating the TLS implementation. Thanks to Jordan Zebor at F5 - Networks all of his help investigating this issue with the Node.js - team.
-
Memory exhaustion DoS on v9.x (CVE-2018-7164)
+ HIGH. An attacker can cause a denial of service (DoS) by causing a + node process which provides an http server supporting TLS server to + crash. This can be accomplished by sending duplicate/unexpected + messages during the handshake. This vulnerability has been addressed + by updating the TLS implementation. Thanks to Jordan Zebor at F5 + Networks all of his help investigating this issue with the Node.js + team.
+
Memory exhaustion DoS on v9.x (CVE-2018-7164)

Versions 9.7.0 and later are vulnerable and the severity is MEDIUM. - A bug introduced in 9.7.0 increases the memory consumed when reading - from the network into JavaScript using the net.Socket object - directly as a stream. An attacker could use this cause a denial of - service by sending tiny chunks of data in short succession. This - vulnerability was restored by reverting to the prior behaviour.
-
Calls to Buffer.fill() and/or Buffer.alloc() may hang (CVE-2018-7167)
+ A bug introduced in 9.7.0 increases the memory consumed when reading + from the network into JavaScript using the net.Socket object + directly as a stream. An attacker could use this cause a denial of + service by sending tiny chunks of data in short succession. This + vulnerability was restored by reverting to the prior behaviour.
+
Calls to Buffer.fill() and/or Buffer.alloc() may hang (CVE-2018-7167)

Calling Buffer.fill() or Buffer.alloc() with some parameters can - lead to a hang which could result in a Denial of Service. In order - to address this vulnerability, the implementations of Buffer.alloc() - and Buffer.fill() were updated so that they zero fill instead of - hanging in these cases.
+ lead to a hang which could result in a Denial of Service. In order + to address this vulnerability, the implementations of Buffer.alloc() + and Buffer.fill() were updated so that they zero fill instead of + hanging in these cases.