Uploaded image for project: 'FUSE Services Framework'
  1. FUSE Services Framework
  2. SF-247

WS-SecurityPolicy SignedElements, SignedParts, EncryptedParts, EncryptedElements, and ContentEncryptedElements assertions incorrectly verified

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.2.2.2-fuse, 2.3.0.0-fuse
    • Fix Version/s: 2.2.6-fuse-01-00
    • Component/s: None
    • Labels:
      None

      Description

      When security configuration is provided via WS-SecurityPolicy, the PolicyBasedWSS4JInInterceptor enforces the SignedElements assertion incorrectly. If there is more than one match to the assertion XPath, the validation code does not correctly detect the unsigned matches so long as any one of the matches is signed. This logic does not accurately reflect the case in which multiple matches for the signature coverage XPath exist in the message and may provide a false sense of integrity in the message.

      Per section 1.2 of the WS-Security spec:
      The XPath expression "identifies the nodes to be integrity protected."

      Based on this language, it seems as if all nodes matching the XPath expression must be integrity constrained.

      Similar issues exist with the SignedParts, EncryptedParts, EncryptedElements, and ContentEncryptedElements assertions as well.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dvaleri David Valeri
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: