cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF > CVE-2013-0239
Date Fri, 08 Feb 2013 11:30:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/9/15/_/styles/combined.css?spaceKey=CXF&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">CVE-2013-0239</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Colm
O hEigeartaigh</a>
    <div class="notificationGreySide">
         <p>----<del>BEGIN PGP SIGNED MESSAGE</del>----<br/>
Hash: SHA1</p>

<p>CVE-2013-0239: Authentication bypass in the case of WS-SecurityPolicy enabled<br/>
plaintext UsernameTokens.</p>

<p>Severity: Critical</p>

<p>Vendor: The Apache Software Foundation</p>

<p>Versions Affected:</p>

<p>This vulnerability affects all versions of Apache CXF prior to 2.5.9, 2.6.6<br/>
and 2.7.3. </p>


<p>The following WS-SecurityPolicy 1.3 fragment requires that a WS-Security<br/>
UsernameToken must be present in the security header of a SOAP request:</p>

<p>&lt;sp:UsernameToken sp:IncludeToken=""&gt;<br/>

<p>If a UsernameToken element is sent with no password child element, then a<br/>
policy similar to the policy defined above will completely bypass<br/>
authentication by default. This is due to the use-case of supporting deriving<br/>
keys from a UsernameToken, where a password element would not be sent in the<br/>

<p>The vulnerability does not apply in any of the following circumstances:</p>

<p> a) You are using a custom UsernameTokenValidator which does not allow the<br/>
    'verifyUnknownPassword' use-case, or that otherwise insists that a password<br/>
    must be present in the token (such as the 'JAASUsernameTokenValidator' in<br/>
 b) You are using a 'sp:HashPassword' policy that requires a hashed password<br/>
    to be present in the token.<br/>
 c) You are using the older style of configuring WS-Security without using<br/>

<p>If you are relying on WS-SecurityPolicy enabled plaintext UsernameTokens to<br/>
authenticate users, and if neither points a) nor b) apply, then you must<br/>
upgrade to a fixed version of CXF (see below), or else configure a custom<br/>
UsernameTokenValidator implementation to insist that a password element must<br/>
be present.</p>

<p>The fix has been to require a password element in the case of a (non-endorsing)<br/>

<p>This has been fixed in revisions:</p>

<p><a href=";revision=1438424"
class="external-link" rel="nofollow">;revision=1438424</a></p>


<p>Users of CXF prior to 2.5.x should upgrade to either 2.5.9, 2.6.6, or 2.7.3.<br/>
CXF 2.5.x users should upgrade to 2.5.9 as soon as possible.<br/>
CXF 2.6.x users should upgrade to 2.6.6 as soon as possible.<br/>
CXF 2.7.x users should upgrade to 2.7.3 as soon as possible.</p>

<p>References: <a href="" class="external-link"

<p>----<del>BEGIN PGP SIGNATURE</del>----<br/>
Version: GnuPG v1.4.11 (GNU/Linux)</p>

----<del>END PGP SIGNATURE</del>----</p>
    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message