coheigea opened a new pull request, #778:
URL: https://github.com/apache/ws-wss4j/pull/778

   Require a processed Timestamp for IncludeTimestamp (StAX policy)
   
   IncludeTimeStampAssertionState was created as asserted, and only a
   TIMESTAMP event could change it, so it never failed for a missing
   Timestamp. Its presence was enforced only by RequiredElements and
   SignedElements assertions on the Timestamp element path, which compare
   QNames and not which Security header the element is in.
   
   A signed Timestamp moved, unchanged, into a Security header for another
   actor/role therefore satisfied the policy: that header is skipped, so
   the Timestamp was never validated and the Timestamp/Signature replay
   cache was never consulted, but its path still matched and its
   signature still verified. An expired message was accepted, and could be
   replayed any number of times.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to