From owner-svn-ports-head@freebsd.org Tue Feb 27 15:22:34 2018 Return-Path: Delivered-To: svn-ports-head@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 A1CB2F2EBBE; Tue, 27 Feb 2018 15:22:34 +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.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 53D3D7D29A; Tue, 27 Feb 2018 15:22:34 +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 4DC8A4636; Tue, 27 Feb 2018 15:22:34 +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 w1RFMYco037663; Tue, 27 Feb 2018 15:22:34 GMT (envelope-from girgen@FreeBSD.org) Received: (from girgen@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w1RFMXKt037661; Tue, 27 Feb 2018 15:22:33 GMT (envelope-from girgen@FreeBSD.org) Message-Id: <201802271522.w1RFMXKt037661@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: girgen set sender to girgen@FreeBSD.org using -f From: Palle Girgensohn Date: Tue, 27 Feb 2018 15:22:33 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r463145 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: girgen X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 463145 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.25 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 15:22:35 -0000 Author: girgen Date: Tue Feb 27 15:22:33 2018 New Revision: 463145 URL: https://svnweb.freebsd.org/changeset/ports/463145 Log: Document security problems with shibboleth-sp Security: CVE-2018-0489 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Tue Feb 27 15:04:47 2018 (r463144) +++ head/security/vuxml/vuln.xml Tue Feb 27 15:22:33 2018 (r463145) @@ -58,6 +58,92 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + shibboleth-sp -- vulnerable to forged user attribute data + + + xmltooling + 1.6.4 + + + xerces-c3 + 3.1.4 + + + + +

Shibboleth consortium reports:

+
+

+ Shibboleth SP software vulnerable to additional data forgery flaws +

+

+ The XML processing performed by the Service Provider software has + been found to be vulnerable to new flaws similar in nature to the + one addressed in an advisory last month. +

+

+ These bugs involve the use of other XML constructs rather than + entity references, and therefore required additional mitigation once + discovered. As with the previous issue, this flaw allows for + changes to an XML document that do not break a digital signature but + can alter the user data passed through to applications behind the SP + and result in impersonation attacks and exposure of protected + information. +

+

+ As before, the use of XML Encryption is a significant mitigation, + but we have not dismissed the possibility that attacks on the + Response "envelope" may be possible, in both the original and this + new case. No actual attacks of this nature are known, so deployers + should prioritize patching systems that expect to handle unencrypted + SAML assertions. +

+

+ An updated version of XMLTooling-C (V1.6.4) is available that + protects against these new attacks, and should help prevent similar + vulnerabilities in the future. +

+

+ Unlike the previous case, these bugs are NOT prevented by any + existing Xerces-C parser version on any platform and cannot be + addressed by any means other than the updated XMLTooling-C library. +

+

+ The Service Provider software relies on a generic XML parser to + process SAML responses and there are limitations in older versions + of the parser that make it impossible to fully disable Document Type + Definition (DTD) processing. +

+

+ Through addition/manipulation of a DTD, it's possible to make + changes to an XML document that do not break a digital signature but + are mishandled by the SP and its libraries. These manipulations can + alter the user data passed through to applications behind the SP and + result in impersonation attacks and exposure of protected + information. +

+

+ While newer versions of the xerces-c3 parser are configured by the + SP into disallowing the use of a DTD via an environment variable, + this feature is not present in the xerces-c3 parser before version + 3.1.4, so an additional fix is being provided now that an actual DTD + exploit has been identified. Xerces-c3-3.1.4 was committed to the + ports tree already on 2016-07-26. +

+
+ +
+ + https://shibboleth.net/community/advisories/secadv_20180227.txt + CVE-2018-0489 + + + 2018-02-27 + 2018-02-27 + +
+ drupal -- Drupal Core - Multiple Vulnerabilities