aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgirgen <girgen@FreeBSD.org>2018-02-27 23:22:33 +0800
committergirgen <girgen@FreeBSD.org>2018-02-27 23:22:33 +0800
commita32f2eef321702736f8dbfb48a04db4cf291b6f8 (patch)
treed6c4a17dd9ca2ccdd6ef7f7ca0191045dd9c9c5a
parentdba8548f96e016e3a6ba393f005ec9d4ee24b014 (diff)
downloadfreebsd-ports-gnome-a32f2eef321702736f8dbfb48a04db4cf291b6f8.tar.gz
freebsd-ports-gnome-a32f2eef321702736f8dbfb48a04db4cf291b6f8.tar.zst
freebsd-ports-gnome-a32f2eef321702736f8dbfb48a04db4cf291b6f8.zip
Document security problems with shibboleth-sp
Security: CVE-2018-0489
-rw-r--r--security/vuxml/vuln.xml86
1 files changed, 86 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index c69065ee64b6..3bc0ee587f1f 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -58,6 +58,92 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="22438240-1bd0-11e8-a2ec-6cc21735f730">
+ <topic>shibboleth-sp -- vulnerable to forged user attribute data</topic>
+ <affects>
+ <package>
+ <name>xmltooling</name>
+ <range><lt>1.6.4</lt></range>
+ </package>
+ <package>
+ <name>xerces-c3</name>
+ <range><lt>3.1.4</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>Shibboleth consortium reports:</p>
+ <blockquote cite="https://shibboleth.net/community/advisories/secadv_20180227.txt">
+ <p>
+ Shibboleth SP software vulnerable to additional data forgery flaws
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <url>https://shibboleth.net/community/advisories/secadv_20180227.txt</url>
+ <cvename>CVE-2018-0489</cvename>
+ </references>
+ <dates>
+ <discovery>2018-02-27</discovery>
+ <entry>2018-02-27</entry>
+ </dates>
+ </vuln>
+
<vuln vid="57580fcc-1a61-11e8-97e0-00e04c1ea73d">
<topic>drupal -- Drupal Core - Multiple Vulnerabilities</topic>
<affects>
s='insertions'>+3 * Update to 1.8.0bapt2014-10-312-3/+6 * KDE/FreeBSD team presents KDE SC 4.14.2 and KDE Workspace 4.11.13!makc2014-10-193-304/+86 * Update to 4.3.2.jkim2014-10-172-5/+4 * Update the default version of GCC in the Ports Collection from GCC 4.7.4gerald2014-09-113-2/+3 * Upgrade OpenEXR and ilmbase to 2.2.0.mandree2014-08-162-1/+2 * Remove indefinite articles and trailing periods from COMMENT, plusolgeni2014-08-033-3/+3 * Convert a bunch of EXTRACT_SUFX=... into USES=tar:...adamw2014-07-302-4/+2 * Modernize LIB_DEPENDSbapt2014-07-151-1/+1 * Stagify.vanilla2014-07-021-8/+4 * Update to 4.2.5.jkim2014-06-241-4/+4 * Update to libreoffice 4.2.4bapt2014-06-111-4/+4 * Support staging.mi2014-06-102-3/+2 * Remove the NO_STAGE. This port is as stage-ready as graphics/gd.mi2014-06-101-2/+1 * KDE/FreeBSD team presents KDE SC 4.12.5 and KDE Workspace 4.11.9!makc2014-05-111-2/+2 * Update to 4.1.6.jkim2014-05-071-4/+4 * KDE/FreeBSD team presents KDE SC 4.12.4 and KDE Workspace 4.11.8!makc2014-04-031-2/+2 * - Update to 1.7.1sunpoet2014-03-312-3/+3 * - Update to 1.7.1sunpoet2014-03-312-3/+3 * Convert u* and v* to USES=zipbapt2014-03-112-2/+2 * KDE/FreeBSD team presents KDE SC 4.12.3 and KDE Workspace 4.11.7!makc2014-03-052-11/+11