lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Thu, 7 Jun 2012 10:41:33 +0100
From: Colm O hEigeartaigh <coheigea@...che.org>
To: users@....apache.org, dev@....apache.org, 
	Apache Security Response Team <security@...che.org>,
	full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: CVE-2012-2379 - Apache CXF does not verify that
 elements were signed or encrypted by a particular Supporting Token.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


CVE-2012-2379: Apache CXF does not verify that elements were signed or
encrypted by a particular Supporting Token.

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:

This vulnerability affects all released versions of Apache CXF.

Description:

Apache CXF currently validates WS-SecurityPolicy SignedParts,
SignedElements,
EncryptedParts and EncryptedElements policies by checking to see if the
matching elements are signed or encrypted if they are included in the
request.
However, CXF does not ensure that the elements were signed or encrypted by
a particular token, if these policies are specified as children of a
Supporting Token. For example, the following policy requires that (the
private
key associated with) an X.509 Token sign the WS-Addressing "To" header. CXF
currently checks to see whether the header was signed, but not by a X.509
Token in particular:

<sp:SupportingToken>
  <sp:X509Token sp:IncludeToken="...">...</sp:X509Token>
  <sp:SignedParts>
        <sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"
/>
  </sp:SignedParts>
</sp:SupportingToken>

Note that this applies for both WS-SecurityPolicy 1.1 and 1.2 policies.

This has been fixed in revision:

http://svn.apache.org/viewvc?rev=1338219&view=rev

All released versions of CXF are affected.

Migration:

Users of CXF prior to 2.4.x should upgrade to either 2.4.8, 2.5.4, or 2.6.1.
CXF 2.4.5 to 2.4.7 users should upgrade to 2.4.8 as soon as possible.
CXF 2.5.1 to 2.5.3 users should upgrade to 2.5.4 as soon as possible.
CXF 2.6.0 users should upgrade to 2.6.1 as soon as possible.

References: http://cxf.apache.org/security-advisories.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJP0HTcAAoJEGe/gLEK1TmDFVwH/Agv7RZZh8osal/xBWENZYKE
LrLK51XzYuASo6B6ezU69HsVmgLpbopl94Rhn7mbKdz0dFG417WbqftXz81PFc0N
UYIh8zNf/SAgm+7onRq9kawFqp28cbP2B1hkhT16q0BEMcB4bJ06YLR8J7VHcyxu
QW//mMuOszVvz1Pn6jlcaQryQ8tvwWPT1Li/L5QmZxmw/M4N9joOEtIp/3kJ+HhX
vW5BW9/9x4BSRU50dF13/viStUqUh5bZDDz1R6qbYm8IDU4F2eC8lc5KcGfBvbM7
uUmVTtsKsdlRo8d2gUL0iyCKp7n+2w9D19Y+gcUvsqKZGwQE/LuryDVNK4EFeBc=
=hkRS
-----END PGP SIGNATURE-----


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists