cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r996966 - in /websites/production/cxf/content: cache/main.pageCache fediz.html security-advisories.data/CVE-2016-4464.txt.asc security-advisories.html
Date Thu, 08 Sep 2016 16:47:37 GMT
Author: buildbot
Date: Thu Sep  8 16:47:37 2016
New Revision: 996966

Log:
Production update by buildbot for cxf

Added:
    websites/production/cxf/content/security-advisories.data/CVE-2016-4464.txt.asc
Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/fediz.html
    websites/production/cxf/content/security-advisories.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/fediz.html
==============================================================================
--- websites/production/cxf/content/fediz.html (original)
+++ websites/production/cxf/content/fediz.html Thu Sep  8 16:47:37 2016
@@ -99,7 +99,7 @@ Apache CXF -- Fediz
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="Fediz-ApacheCXFFediz:AnOpen-SourceWebSecurityFramework">Apache
CXF Fediz: An Open-Source Web Security Framework</h1><h2 id="Fediz-Overview">Overview</h2><p>Apache
CXF Fediz is a subproject of CXF. Fediz helps you to secure your web applications and delegates
security enforcement to the underlying application server. With Fediz, authentication is externalized
from your web application to an identity provider installed as a dedicated server component.
The supported standard is <a shape="rect" class="external-link" href="http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175002"
rel="nofollow">WS-Federation Passive Requestor Profile</a>. Fediz supports <a
shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Claims-based_identity"
rel="nofollow">Claims Based Access Control</a> beyond Role Based Access Control (RBAC).</p><h2
id="Fediz-News">News</h2><p><strong><strong>March 30, 2016 - Apache
CXF F
 ediz 1.3.0 released<br clear="none"></strong></strong></p><p>Apache
CXF Fediz 1.3.0 has been released. It contains an update to use CXF 3.1.6, a new OpenId Connect
based IdP (<a shape="rect" href="fediz-oidc.html">Fediz OIDC</a>), support for
bridging between the WS-Federation and OpenId Connect protocols, and support for SAML SSO
in the Fediz IdP.</p><p>For more information and to download the new releases,
please go <a shape="rect" href="fediz-downloads.html">here</a>.</p><p><strong><strong>February
16, 2016 - Apache CXF Fediz 1.2.2 released<br clear="none"></strong></strong></p><p>Apache
CXF Fediz 1.2.2 has been released. It contains an update to use CXF 3.0.8, some updates to
the Websphere plugin, a fix for some issues relating to caching SAML tokens, and various other
bug fixes.</p><p>For more information and to download the new releases, please
go <a shape="rect" href="fediz-downloads.html">here</a>.</p><p><strong>August
28, 2015 - A new security advisory for Apache CXF Fediz 
 is released</strong></p><p>A security issue was fixed in the latest Fediz
releases (1.2.1 + 1.1.3):</p><ul><li><a shape="rect" href="http://cxf.apache.org/security-advisories.data/CVE-2015-5175.txt.asc?version=1&amp;modificationDate=1440598018000&amp;api=v2">CVE-2015-5175</a>:
Apache CXF Fediz application plugins are vulnerable to Denial of Service (DoS) attacks</li></ul><p>Please
upgrade to the latest releases as soon as possible.</p><h2 id="Fediz-Features">Features</h2><p>The
following features are supported by Fediz 1.2</p><ul><li>WS-Federation 1.0/1.1/1.2</li><li>SAML
1.1/2.0 Tokens</li><li>Support for encrypted SAML Tokens (Release 1.1)</li><li>Support
for Holder-Of-Key SubjectConfirmationMethod (1.1)</li><li>Custom token Support</li><li>Publish
WS-Federation Metadata document</li><li>Role information encoded as AttributeStatement
in SAML 1.1/2.0 tokens</li><li>Claims information provided by FederationPrincipal
Interface</li><li>Support for Tomcat, Jetty, Websphere, Spring Secu
 rity and CXF (1.1)</li><li>Fediz IDP supports "Resource IDP" role as well (1.1)</li><li>A
new REST API for the IdP (1.2)</li><li>Support for logout in both the RP and IdP
(1.2)</li><li>Support for logging on to the IdP via Kerberos and TLS client authentication
(1.2)</li><li>A new container-independent CXF plugin for WS-Federation (1.2)</li><li>Support
to use the IdP as an identity broker with a remote SAML SSO IdP (1.2)</li></ul><p>The
following features are planned for the next release:</p><ul><li>support
for other protocols like OAuth</li></ul><p>You can get the current status
of the enhancements <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/FEDIZ">here
</a>.</p><h2 id="Fediz-Architecture">Architecture</h2><p>The
Fediz architecture is described in more detail <a shape="rect" href="fediz-architecture.html">here</a>.</p><h2
id="Fediz-Download">Download</h2><p>See <a shape="rect" href="fediz-downloads.html">here</a>.</p><h2
id="Fediz-Gettingstarte
 d">Getting started</h2><p>The WS-Federation specification defines the following
parties involved during a web login:</p><ul><li>Browser</li><li>Identity
Provider (IDP)<br clear="none"> The IDP is a centralized, application independent runtime
component which implements the protocol defined by WS-Federation. You can use any open source
or commercial product that supports WS-Federation 1.1/1.2 as your IDP. It's recommended to
use the Fediz IDP for testing as it allows for testing your web application in a sandbox without
having all infrastructure components available. The Fediz IDP consists of two WAR components.
The Security Token Service (STS) does most of the work including user authentication, claims/role
data retrieval and creating the SAML token. The IDP WAR translates the response to an HTML
response allowing a browser to process it.</li><li>Relying Party (RP)<br clear="none">
The RP is a web application that needs to be protected. The RP must be able to implement the
protocol 
 as defined by WS-Federation. This component is called "Fediz Plugin" in this project which
consists of container agnostic module/jar and a container specific jar. When an authenticated
request is detected by the plugin it redirects to the IDP for authentication. The browser
sends the response from the IDP to the RP after successful authentication. The RP validates
the response and creates the container security context.</li></ul><p>It's
recommended to deploy the IDP and the web application (RP) into different container instances
as in a production deployment. The container with the IDP can be used during development and
testing for multiple web applications needing security.</p><h3 id="Fediz-SettinguptheIDP">Setting
up the IDP</h3><p>The installation and configuration of the IDP is documented
<a shape="rect" href="fediz-idp-11.html">here</a></p><h3 id="Fediz-SetuptheRelyingPartyContainer">Set
up the Relying Party Container</h3><p>The Fediz plugin needs to be deployed into
the Relyin
 g Party (RP) container. The security mechanism is not specified by JEE. Even though it is
very similar in each servlet container there are some differences which require a dedicated
Fediz plugin for each servlet container implementation. Most of the configuration goes into
a Servlet container independent configuration file which is described <a shape="rect" href="fediz-configuration.html">here</a></p><p>The
following lists shows the supported containers and the location of the installation and configuration
page.</p><ul><li><a shape="rect" href="fediz-tomcat.html">Tomcat 7
</a></li><li><a shape="rect" href="fediz-jetty.html">Jetty 7/8 (1.1)</a></li><li><a
shape="rect" href="fediz-spring.html">Spring Security 3.1 (1.1)</a></li><li><a
shape="rect" href="fediz-websphere.html">Websphere 7/8 (1.1)</a></li><li><a
shape="rect" href="fediz-cxf.html">CXF (1.1) </a></li></ul><h2 id="Fediz-Samples">Samples</h2><p>The
examples directory contains two sample relying party applications. They are i
 ndependent of each other, so it is not necessary to deploy both at once.</p><p>Each
sample is described in a <code>README.txt</code> file located in the base directory
of each sample.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Sample</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>simpleWebapp</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>a simple web application which is
protected by the Fediz IDP. The FederationServlet illustrates how to get security information
using the standard APIs.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>wsclientWebapp</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>a protected web application that
calls a web service that uses the Fediz STS to validate credentials. Here, the same STS is
used for token i
 ssuance (indirectly, by the web application through use of the Fediz IDP) and validation.
The FederationServlet illustrates how to securely call a web service.</p></td></tr></tbody></table></div><p><span
class="confluence-anchor-link" id="Fediz-building"></span></p><h2 id="Fediz-Building">Building</h2><p>Check
out the code from here:</p><ul><li>git clone -v <a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/repos/asf/cxf-fediz.git">https://git-wip-us.apache.org/repos/asf/cxf-fediz.git</a></li></ul><p>Then
follow the <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/fediz/trunk/BUILDING.txt?view=markup">BUILDING.txt</a>
file in the Fediz download for full build instructions.</p><h5 id="Fediz-SettingupEclipse:">Setting
up Eclipse:</h5><p>See <a shape="rect" href="http://cxf.apache.org/setting-up-eclipse.html">this
page</a> for information on using the Eclipse IDE with the Fediz source code. This page
is created for CXF but the same com
 mands are applicable for Fediz too.</p></div>
+<div id="ConfluenceContent"><h1 id="Fediz-ApacheCXFFediz:AnOpen-SourceWebSecurityFramework">Apache
CXF Fediz: An Open-Source Web Security Framework</h1><h2 id="Fediz-Overview">Overview</h2><p>Apache
CXF Fediz is a subproject of CXF. Fediz helps you to secure your web applications and delegates
security enforcement to the underlying application server. With Fediz, authentication is externalized
from your web application to an identity provider installed as a dedicated server component.
The supported standard is <a shape="rect" class="external-link" href="http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175002"
rel="nofollow">WS-Federation Passive Requestor Profile</a>. Fediz supports <a
shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Claims-based_identity"
rel="nofollow">Claims Based Access Control</a> beyond Role Based Access Control (RBAC).</p><h2
id="Fediz-News">News</h2><p><strong><strong>September 8, 2016 -
Apache CX
 F Fediz 1.3.1 and 1.2.3 released<br clear="none"></strong></strong></p><p>Apache
CXF Fediz 1.3.1 and 1.2.3 have been released.</p><p>For more information and to
download the new releases, please go <a shape="rect" href="fediz-downloads.html">here</a>.</p><p><strong><strong><strong>September
8, 2016</strong></strong>&#160;- A new security advisory for Apache CXF Fediz
is released</strong></p><p>A security issue was fixed in the latest Fediz
releases (1.3.1 + 1.2.3):</p><ul><li><a shape="rect" href="http://cxf.apache.org/security-advisories.data/CVE-2015-5175.txt.asc?version=1&amp;modificationDate=1440598018000&amp;api=v2">CVE-2016-4464</a>:
Apache CXF Fediz application plugins do not match the SAML AudienceRestriction values against
the list of configured audience URIs</li></ul><p>Please upgrade to the latest
releases as soon as possible.</p><h2 id="Fediz-Features">Features</h2><p>The
following features are supported by Fediz 1.2</p><ul><li>WS-Federation 1.0/1.1/1.2</li><li>SAML
1.1/
 2.0 Tokens</li><li>Support for encrypted SAML Tokens (Release 1.1)</li><li>Support
for Holder-Of-Key SubjectConfirmationMethod (1.1)</li><li>Custom token Support</li><li>Publish
WS-Federation Metadata document</li><li>Role information encoded as AttributeStatement
in SAML 1.1/2.0 tokens</li><li>Claims information provided by FederationPrincipal
Interface</li><li>Support for Tomcat, Jetty, Websphere, Spring Security and CXF
(1.1)</li><li>Fediz IDP supports "Resource IDP" role as well (1.1)</li><li>A
new REST API for the IdP (1.2)</li><li>Support for logout in both the RP and IdP
(1.2)</li><li>Support for logging on to the IdP via Kerberos and TLS client authentication
(1.2)</li><li>A new container-independent CXF plugin for WS-Federation (1.2)</li><li>Support
to use the IdP as an identity broker with a remote SAML SSO IdP (1.2)</li></ul><p>The
following features are planned for the next release:</p><ul><li>support
for other protocols like OAuth</li></ul><p>You can get the current sta
 tus of the enhancements <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/FEDIZ">here
</a>.</p><h2 id="Fediz-Architecture">Architecture</h2><p>The
Fediz architecture is described in more detail <a shape="rect" href="fediz-architecture.html">here</a>.</p><h2
id="Fediz-Download">Download</h2><p>See <a shape="rect" href="fediz-downloads.html">here</a>.</p><h2
id="Fediz-Gettingstarted">Getting started</h2><p>The WS-Federation specification
defines the following parties involved during a web login:</p><ul><li>Browser</li><li>Identity
Provider (IDP)<br clear="none"> The IDP is a centralized, application independent runtime
component which implements the protocol defined by WS-Federation. You can use any open source
or commercial product that supports WS-Federation 1.1/1.2 as your IDP. It's recommended to
use the Fediz IDP for testing as it allows for testing your web application in a sandbox without
having all infrastructure components available. The Fediz 
 IDP consists of two WAR components. The Security Token Service (STS) does most of the work
including user authentication, claims/role data retrieval and creating the SAML token. The
IDP WAR translates the response to an HTML response allowing a browser to process it.</li><li>Relying
Party (RP)<br clear="none"> The RP is a web application that needs to be protected.
The RP must be able to implement the protocol as defined by WS-Federation. This component
is called "Fediz Plugin" in this project which consists of container agnostic module/jar and
a container specific jar. When an authenticated request is detected by the plugin it redirects
to the IDP for authentication. The browser sends the response from the IDP to the RP after
successful authentication. The RP validates the response and creates the container security
context.</li></ul><p>It's recommended to deploy the IDP and the web application
(RP) into different container instances as in a production deployment. The container wit
 h the IDP can be used during development and testing for multiple web applications needing
security.</p><h3 id="Fediz-SettinguptheIDP">Setting up the IDP</h3><p>The
installation and configuration of the IDP is documented <a shape="rect" href="fediz-idp-11.html">here</a></p><h3
id="Fediz-SetuptheRelyingPartyContainer">Set up the Relying Party Container</h3><p>The
Fediz plugin needs to be deployed into the Relying Party (RP) container. The security mechanism
is not specified by JEE. Even though it is very similar in each servlet container there are
some differences which require a dedicated Fediz plugin for each servlet container implementation.
Most of the configuration goes into a Servlet container independent configuration file which
is described <a shape="rect" href="fediz-configuration.html">here</a></p><p>The
following lists shows the supported containers and the location of the installation and configuration
page.</p><ul><li><a shape="rect" href="fediz-tomcat.html">Tomcat 7
</a
 ></li><li><a shape="rect" href="fediz-jetty.html">Jetty 7/8 (1.1)</a></li><li><a
shape="rect" href="fediz-spring.html">Spring Security 3.1 (1.1)</a></li><li><a
shape="rect" href="fediz-websphere.html">Websphere 7/8 (1.1)</a></li><li><a
shape="rect" href="fediz-cxf.html">CXF (1.1) </a></li></ul><h2 id="Fediz-Samples">Samples</h2><p>The
examples directory contains two sample relying party applications. They are independent of
each other, so it is not necessary to deploy both at once.</p><p>Each sample is
described in a <code>README.txt</code> file located in the base directory of each
sample.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Sample</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>simpleWebapp</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>a simple web application which is
protec
 ted by the Fediz IDP. The FederationServlet illustrates how to get security information using
the standard APIs.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>wsclientWebapp</strong></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>a protected web application that
calls a web service that uses the Fediz STS to validate credentials. Here, the same STS is
used for token issuance (indirectly, by the web application through use of the Fediz IDP)
and validation. The FederationServlet illustrates how to securely call a web service.</p></td></tr></tbody></table></div><p><span
class="confluence-anchor-link" id="Fediz-building"></span></p><h2 id="Fediz-Building">Building</h2><p>Check
out the code from here:</p><ul><li>git clone -v <a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/repos/asf/cxf-fediz.git">https://git-wip-us.apache.org/repos/asf/cxf-fediz.git</a></li></ul><p>Then
follow the <a shape="rect" class="external-link" 
 href="http://svn.apache.org/viewvc/cxf/fediz/trunk/BUILDING.txt?view=markup">BUILDING.txt</a>
file in the Fediz download for full build instructions.</p><h5 id="Fediz-SettingupEclipse:">Setting
up Eclipse:</h5><p>See <a shape="rect" href="http://cxf.apache.org/setting-up-eclipse.html">this
page</a> for information on using the Eclipse IDE with the Fediz source code. This page
is created for CXF but the same commands are applicable for Fediz too.</p></div>
            </div>
            <!-- Content -->
          </td>

Added: websites/production/cxf/content/security-advisories.data/CVE-2016-4464.txt.asc
==============================================================================
--- websites/production/cxf/content/security-advisories.data/CVE-2016-4464.txt.asc (added)
+++ websites/production/cxf/content/security-advisories.data/CVE-2016-4464.txt.asc Thu Sep
 8 16:47:37 2016
@@ -0,0 +1,49 @@
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+CVE-2016-4464: Apache CXF Fediz application plugins do not match the SAML
+AudienceRestriction values against the list of configured audience URIs.
+
+Severity: Minor
+
+Vendor: The Apache Software Foundation
+
+Versions Affected:
+
+This vulnerability affects Apache CXF Fediz 1.2.0, 1.2.1, 1.2.2 and 1.3.0.
+
+Description:
+
+Apache CXF Fediz is a subproject of Apache CXF which implements the
+WS-Federation Passive Requestor Profile for SSO specification. It provides a
+number of container based plugins to enable SSO for Relying Party applications.
+It is possible to configure a list of audience URIs for the plugins, against
+which the AudienceRestriction values of the received SAML tokens are supposed
+to be matched. However, this matching does not actually take place.
+
+This means that a token could be accepted by the application plugin (assuming
+that the signature is trusted) that is targeted for another service, something
+that could potentially be exploited by an attacker.
+
+This has been fixed in revision:
+
+https://git-wip-us.apache.org/repos/asf?p=cxf-fediz.git;a=commit;h=0006581e9cacbeef46381a223e5671e524d416b6
+
+Migration:
+
+Fediz 1.1.x users are not effected by this vulnerability.
+Fediz 1.2.x users should upgrade to 1.2.3 or later as soon as possible.
+Fediz 1.3.x users should upgrade to 1.3.1 or later as soon as possible.
+
+References: http://cxf.apache.org/security-advisories.html
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1
+
+iQEcBAEBAgAGBQJX0YdhAAoJEGe/gLEK1TmDiwcH/ihVpJqEM1vFOqxAOxMJ7mHp
+jNyyF6v/iE++4p5/gPIaJj8ULlqZb1jFs2kU2x6WF+YWAVoCzjF719Kp5a/nAL5N
+7BiUbH9Knio+hRiQvgBKXxNOhGUt+cFvJJK72EKv32KIZtmMjQJVTYL+dChKEOv1
+361dCDWCIZBU1EqoYnkd6eN9wuV64P+jSu3nylhztt3Vas7lfGevVw4kG5zm9B35
+2vZ3EylaxMjC4j7QjLl3KdOyCgXfSOYK2gdGJdIvBwiI5Nc1jH+wCP9+Q3O9ABUP
+oq5pUgWrFxyJT9oxYBTm6Vfoh1N28UU4OLksyhiwmVIbMlg4clGqSXpQ6KINN18=
+=2TfQ
+-----END PGP SIGNATURE-----

Modified: websites/production/cxf/content/security-advisories.html
==============================================================================
--- websites/production/cxf/content/security-advisories.html (original)
+++ websites/production/cxf/content/security-advisories.html Thu Sep  8 16:47:37 2016
@@ -99,7 +99,7 @@ Apache CXF -- Security Advisories
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h3 id="SecurityAdvisories-2015">2015</h3><ul><li><a
shape="rect" href="security-advisories.data/CVE-2015-5253.txt.asc?version=1&amp;modificationDate=1447433340000&amp;api=v2"
data-linked-resource-id="61328642" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2015-5253.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2015-5253</a>:
Apache CXF SAML SSO processing is vulnerable to a wrapping attack</li><li><a
shape="rect" href="security-advisories.data/CVE-2015-5175.txt.asc?version=1&amp;modificationDate=1440598018000&amp;api=v2"
data-linked-resource-id="61316328" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2015-5175.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-
 linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2015-5175</a>:
Apache CXF Fediz application plugins are vulnerable to Denial of Service (DoS) attacks</li></ul><h3
id="SecurityAdvisories-2014">2014</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2014-3577.txt.asc?version=1&amp;modificationDate=1419245371000&amp;api=v2"
data-linked-resource-id="51183657" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-3577.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2014-3577</a>:
Apache CXF SSL hostname verification bypass</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3566.txt.asc?version=1&amp;modificationDate=1418740474000&amp;api=v2"
data-linked-resource-id="50561078" data-linked-resource-version="1" data-linked-resource-type="a
 ttachment" data-linked-resource-default-alias="CVE-2014-3566.txt.asc" data-nice-type="Text
File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="27837502"
data-linked-resource-container-version="21">Note on CVE-2014-3566</a>: SSL 3.0 support
in Apache CXF, aka the "POODLE" attack.</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3623.txt.asc?version=1&amp;modificationDate=1414169368000&amp;api=v2"
data-linked-resource-id="47743195" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-3623.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2014-3623</a>:
Apache CXF does not properly enforce the security semantics of SAML SubjectConfirmation methods
when used with the TransportBinding</li><li><a shape="rect" href="security-advisories.data/CVE-2014-358
 4.txt.asc?version=1&amp;modificationDate=1414169326000&amp;api=v2" data-linked-resource-id="47743194"
data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3584.txt.asc"
data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="27837502"
data-linked-resource-container-version="21">CVE-2014-3584</a>: Apache CXF JAX-RS
SAML handling is vulnerable to a Denial of Service (DoS) attack</li><li><a
shape="rect" href="security-advisories.data/CVE-2014-0109.txt.asc?version=1&amp;modificationDate=1398873370000&amp;api=v2"
data-linked-resource-id="40895138" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0109.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2014-0109</a>:
HTML content poste
 d to SOAP endpoint could cause OOM errors</li><li><a shape="rect" href="security-advisories.data/CVE-2014-0110.txt.asc?version=1&amp;modificationDate=1398873378000&amp;api=v2"
data-linked-resource-id="40895139" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0110.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2014-0110</a>:
Large invalid content could cause temporary space to fill</li><li><a shape="rect"
href="security-advisories.data/CVE-2014-0034.txt.asc?version=1&amp;modificationDate=1398873385000&amp;api=v2"
data-linked-resource-id="40895140" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0034.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="278375
 02" data-linked-resource-container-version="21">CVE-2014-0034</a>: The SecurityTokenService
accepts certain invalid SAML Tokens as valid</li><li><a shape="rect" href="security-advisories.data/CVE-2014-0035.txt.asc?version=1&amp;modificationDate=1398873391000&amp;api=v2"
data-linked-resource-id="40895141" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0035.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2014-0035</a>:
UsernameTokens are sent in plaintext with a Symmetric EncryptBeforeSigning policy</li></ul><h3
id="SecurityAdvisories-2013">2013</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2013-2160.txt.asc?version=1&amp;modificationDate=1372324301000&amp;api=v2"
data-linked-resource-id="33095710" data-linked-resource-version="1" data-linked-resource-type="attachment"
data
 -linked-resource-default-alias="CVE-2013-2160.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="21">CVE-2013-2160</a>
- Denial of Service Attacks on Apache CXF</li><li><a shape="rect" href="cve-2012-5575.html">Note
on CVE-2012-5575</a> - XML Encryption backwards compatibility attack on Apache CXF.</li><li><a
shape="rect" href="cve-2013-0239.html">CVE-2013-0239</a> - Authentication bypass
in the case of WS-SecurityPolicy enabled plaintext UsernameTokens.</li></ul><h3
id="SecurityAdvisories-2012">2012</h3><ul><li><a shape="rect" href="cve-2012-5633.html">CVE-2012-5633</a>
- WSS4JInInterceptor always allows HTTP Get requests from browser.</li><li><a
shape="rect" href="note-on-cve-2011-2487.html">Note on CVE-2011-2487</a> - Bleichenbacher
attack against distributed symmetric key in WS-Security.</li><li><a shape="rect"
href="cve-2012-3451.html">CVE-2012-3451</a> - Apache 
 CXF is vulnerable to SOAP Action spoofing attacks on Document Literal web services.</li><li><a
shape="rect" href="cve-2012-2379.html">CVE-2012-2379</a> - Apache CXF does not verify
that elements were signed or encrypted by a particular Supporting Token.</li><li><a
shape="rect" href="cve-2012-2378.html">CVE-2012-2378</a> - Apache CXF does not pick
up some child policies of WS-SecurityPolicy 1.1 SupportingToken policy assertions on the client
side.</li><li><a shape="rect" href="note-on-cve-2011-1096.html">Note on
CVE-2011-1096</a> - XML Encryption flaw / Character pattern encoding attack.</li><li><a
shape="rect" href="cve-2012-0803.html">CVE-2012-0803</a> - Apache CXF does not validate
UsernameToken policies correctly.</li></ul><h3 id="SecurityAdvisories-2010">2010</h3><ul><li><a
shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/cxf/trunk/security/CVE-2010-2076.pdf">CVE-2010-2076</a>
- DTD based XML attacks.</li></ul></div>
+<div id="ConfluenceContent"><h3 id="SecurityAdvisories-2016">2016</h3><ul><li><a
shape="rect" href="security-advisories.data/CVE-2016-4464.txt.asc?version=1&amp;modificationDate=1473350153000&amp;api=v2"
data-linked-resource-id="65869472" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2016-4464.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2016-4464</a>:
Apache CXF Fediz application plugins do not match the SAML AudienceRestriction values against
the list of configured audience URIs</li></ul><h3 id="SecurityAdvisories-2015">2015</h3><ul><li><a
shape="rect" href="security-advisories.data/CVE-2015-5253.txt.asc?version=1&amp;modificationDate=1447433340000&amp;api=v2"
data-linked-resource-id="61328642" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-d
 efault-alias="CVE-2015-5253.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2015-5253</a>:
Apache CXF SAML SSO processing is vulnerable to a wrapping attack</li><li><a
shape="rect" href="security-advisories.data/CVE-2015-5175.txt.asc?version=1&amp;modificationDate=1440598018000&amp;api=v2"
data-linked-resource-id="61316328" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2015-5175.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2015-5175</a>:
Apache CXF Fediz application plugins are vulnerable to Denial of Service (DoS) attacks</li></ul><h3
id="SecurityAdvisories-2014">2014</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2014-3577.txt.asc?version=1&amp;m
 odificationDate=1419245371000&amp;api=v2" data-linked-resource-id="51183657" data-linked-resource-version="1"
data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3577.txt.asc"
data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="27837502"
data-linked-resource-container-version="22">CVE-2014-3577</a>: Apache CXF SSL hostname
verification bypass</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3566.txt.asc?version=1&amp;modificationDate=1418740474000&amp;api=v2"
data-linked-resource-id="50561078" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-3566.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">Note
on CVE-2014-3566</a>: SSL 3.0 support in Apache CXF, aka the "POODLE" attack.</li><li><a
shape=
 "rect" href="security-advisories.data/CVE-2014-3623.txt.asc?version=1&amp;modificationDate=1414169368000&amp;api=v2"
data-linked-resource-id="47743195" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-3623.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2014-3623</a>:
Apache CXF does not properly enforce the security semantics of SAML SubjectConfirmation methods
when used with the TransportBinding</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3584.txt.asc?version=1&amp;modificationDate=1414169326000&amp;api=v2"
data-linked-resource-id="47743194" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-3584.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-conta
 iner-id="27837502" data-linked-resource-container-version="22">CVE-2014-3584</a>:
Apache CXF JAX-RS SAML handling is vulnerable to a Denial of Service (DoS) attack</li><li><a
shape="rect" href="security-advisories.data/CVE-2014-0109.txt.asc?version=1&amp;modificationDate=1398873370000&amp;api=v2"
data-linked-resource-id="40895138" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0109.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2014-0109</a>:
HTML content posted to SOAP endpoint could cause OOM errors</li><li><a shape="rect"
href="security-advisories.data/CVE-2014-0110.txt.asc?version=1&amp;modificationDate=1398873378000&amp;api=v2"
data-linked-resource-id="40895139" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0110.
 txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="27837502"
data-linked-resource-container-version="22">CVE-2014-0110</a>: Large invalid content
could cause temporary space to fill</li><li><a shape="rect" href="security-advisories.data/CVE-2014-0034.txt.asc?version=1&amp;modificationDate=1398873385000&amp;api=v2"
data-linked-resource-id="40895140" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2014-0034.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2014-0034</a>:
The SecurityTokenService accepts certain invalid SAML Tokens as valid</li><li><a
shape="rect" href="security-advisories.data/CVE-2014-0035.txt.asc?version=1&amp;modificationDate=1398873391000&amp;api=v2"
data-linked-resource-id="40895141" data-linked-resource-versio
 n="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-0035.txt.asc"
data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="27837502"
data-linked-resource-container-version="22">CVE-2014-0035</a>: UsernameTokens are
sent in plaintext with a Symmetric EncryptBeforeSigning policy</li></ul><h3
id="SecurityAdvisories-2013">2013</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2013-2160.txt.asc?version=1&amp;modificationDate=1372324301000&amp;api=v2"
data-linked-resource-id="33095710" data-linked-resource-version="1" data-linked-resource-type="attachment"
data-linked-resource-default-alias="CVE-2013-2160.txt.asc" data-nice-type="Text File" data-linked-resource-content-type="text/plain"
data-linked-resource-container-id="27837502" data-linked-resource-container-version="22">CVE-2013-2160</a>
- Denial of Service Attacks on Apache CXF</li><li><a shape="rect" href="cve-2012-5575.html">Note

 on CVE-2012-5575</a> - XML Encryption backwards compatibility attack on Apache CXF.</li><li><a
shape="rect" href="cve-2013-0239.html">CVE-2013-0239</a> - Authentication bypass
in the case of WS-SecurityPolicy enabled plaintext UsernameTokens.</li></ul><h3
id="SecurityAdvisories-2012">2012</h3><ul><li><a shape="rect" href="cve-2012-5633.html">CVE-2012-5633</a>
- WSS4JInInterceptor always allows HTTP Get requests from browser.</li><li><a
shape="rect" href="note-on-cve-2011-2487.html">Note on CVE-2011-2487</a> - Bleichenbacher
attack against distributed symmetric key in WS-Security.</li><li><a shape="rect"
href="cve-2012-3451.html">CVE-2012-3451</a> - Apache CXF is vulnerable to SOAP Action
spoofing attacks on Document Literal web services.</li><li><a shape="rect"
href="cve-2012-2379.html">CVE-2012-2379</a> - Apache CXF does not verify that elements
were signed or encrypted by a particular Supporting Token.</li><li><a shape="rect"
href="cve-2012-2378.html">CVE-2012-2378</a> - Apache CX
 F does not pick up some child policies of WS-SecurityPolicy 1.1 SupportingToken policy assertions
on the client side.</li><li><a shape="rect" href="note-on-cve-2011-1096.html">Note
on CVE-2011-1096</a> - XML Encryption flaw / Character pattern encoding attack.</li><li><a
shape="rect" href="cve-2012-0803.html">CVE-2012-0803</a> - Apache CXF does not validate
UsernameToken policies correctly.</li></ul><h3 id="SecurityAdvisories-2010">2010</h3><ul><li><a
shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/cxf/trunk/security/CVE-2010-2076.pdf">CVE-2010-2076</a>
- DTD based XML attacks.</li></ul></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message