Bug 681916 (CVE-2011-1096)

Summary: CVE-2011-1096 jbossws: Prone to character encoding pattern attack (XML Encryption flaw)
Product: [Other] Security Response Reporter: Jan Lieskovsky <jlieskov>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: asoldano, djorm, dwalluck, fnasser, hfnukal, pcheung, rcvalle, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: impact=important,public=20111019,reported=20110215,source=researcher,cvss2=7.8/AV:N/AC:L/Au:N/C:C/I:N/A:N,brms-5/Security=affected,epp-5/cxf=affected,soap-5/cxf=affected,cwe=CWE-327
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 16:03:35 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 757636, 855247, 855248, 855249, 910980, 910981    
Bug Blocks: 713551, 745417, 789173, 835396, 849517    

Description Jan Lieskovsky 2011-03-03 10:22:49 EST
Tibor Jager, Juraj Somorovsky, Meiko Jensen, and Jorg Schwenk
described an attack technique against W3C XML Encryption Standard,
when the block ciphers were used in cipher-block chaining (CBC)
mode of operation. A remote attacker, aware of a cryptographic
weakness of the CBC mode could use this flaw to conduct
chosen-ciphertext attacks, leading to the recovery of the entire
plaintext of a particular cryptogram by examining of the differences
between SOAP responses, sent from JBossWS, J2EE Web Services server.

Acknowledgements:

Red Hat would like to thank Juraj Somorovsky of Ruhr-University Bochum
for reporting this issue.
Comment 12 Jan Lieskovsky 2011-03-09 10:52:27 EST
The CVE identifier of CVE-2011-1096 has been assigned to this issue.
Comment 46 Jan Lieskovsky 2011-11-18 12:45:01 EST
*** Bug 745407 has been marked as a duplicate of this bug. ***
Comment 48 David Jorm 2012-03-11 22:43:19 EDT
This issue is now resolved in JBoss AS 7.1.1.Final.
Comment 53 Murray McAllister 2012-10-03 03:11:19 EDT
When a fix is made available for the product you are using, the fix will
not be automatically applied. After installing the fix, configure your
applications that use WS-Security encryption to use GCM-based algorithms by
editing their WSDL file. The following example uses an AES-128 Algorithm
with GCM mode:

<sp:AlgorithmSuite>
    <wsp:Policy>
        <sp-cxf:Basic128GCM xmlns:sp-cxf="http://cxf.apache.org/custom/security-policy"/>
    </wsp:Policy>
</sp:AlgorithmSuite>

For JBoss Enterprise Application 4.3.0 and other JBoss 4.x products, you should instead update the encrypt element of all jboss-ws-security configuration to specify a GCM algorithm. The following is an example directive: 

<encrypt type="x509v3" algorithm="aes-128-gcm" alias="wsse" />
Comment 54 errata-xmlrpc 2012-10-03 11:10:12 EDT
This issue has been addressed in following products:

  JBoss Enterprise SOA Platform 5.3.0

Via RHSA-2012:1330 https://rhn.redhat.com/errata/RHSA-2012-1330.html
Comment 55 errata-xmlrpc 2012-10-08 12:43:41 EDT
This issue has been addressed in following products:

  JBoss Enterprise Portal Platform 5.2.2

Via RHSA-2012:1344 https://rhn.redhat.com/errata/RHSA-2012-1344.html
Comment 56 errata-xmlrpc 2013-01-24 13:08:51 EST
This issue has been addressed in following products:

  JBoss Enterprise Application Platform 5.2.0

Via RHSA-2013:0194 https://rhn.redhat.com/errata/RHSA-2013-0194.html
Comment 57 errata-xmlrpc 2013-01-24 13:32:08 EST
This issue has been addressed in following products:

  JBEAP 5 for RHEL 5

Via RHSA-2013:0192 https://rhn.redhat.com/errata/RHSA-2013-0192.html
Comment 58 errata-xmlrpc 2013-01-24 13:32:54 EST
This issue has been addressed in following products:

  JBEAP 5 for RHEL 6

Via RHSA-2013:0191 https://rhn.redhat.com/errata/RHSA-2013-0191.html
Comment 59 errata-xmlrpc 2013-01-24 13:45:12 EST
This issue has been addressed in following products:

  JBEWP 5 for RHEL 6

Via RHSA-2013:0195 https://rhn.redhat.com/errata/RHSA-2013-0195.html
Comment 60 errata-xmlrpc 2013-01-24 13:45:57 EST
This issue has been addressed in following products:

  JBEAP 5 for RHEL 4

Via RHSA-2013:0193 https://rhn.redhat.com/errata/RHSA-2013-0193.html
Comment 61 errata-xmlrpc 2013-01-24 13:58:12 EST
This issue has been addressed in following products:

  JBEWP 5 for RHEL 4

Via RHSA-2013:0197 https://rhn.redhat.com/errata/RHSA-2013-0197.html
Comment 62 errata-xmlrpc 2013-01-24 13:59:04 EST
This issue has been addressed in following products:

  JBEWP 5 for RHEL 5

Via RHSA-2013:0196 https://rhn.redhat.com/errata/RHSA-2013-0196.html
Comment 63 errata-xmlrpc 2013-01-24 14:07:53 EST
This issue has been addressed in following products:

  JBoss Enterprise Web Platform 5.2.0

Via RHSA-2013:0198 https://rhn.redhat.com/errata/RHSA-2013-0198.html
Comment 64 errata-xmlrpc 2013-01-31 15:30:48 EST
This issue has been addressed in following products:

  JBoss Enterprise BRMS Platform 5.3.1

Via RHSA-2013:0221 https://rhn.redhat.com/errata/RHSA-2013-0221.html
Comment 65 errata-xmlrpc 2013-02-14 13:32:51 EST
This issue has been addressed in following products:

 JBoss Enterprise Application Platform 4.3.0 CP10

Via RHSA-2013:0261 https://rhn.redhat.com/errata/RHSA-2013-0261.html
Comment 66 errata-xmlrpc 2013-02-26 13:19:12 EST
This issue has been addressed in following products:

  JBoss Enterprise SOA Platform 4.3 CP05
  JBoss Enterprise Portal Platform 4.3 CP07

Via RHSA-2013:0569 https://rhn.redhat.com/errata/RHSA-2013-0569.html