2009 IEEE International Conference on Web Services 2009
DOI: 10.1109/icws.2009.12
|View full text |Cite
|
Sign up to set email alerts
|

Analysis of Signature Wrapping Attacks and Countermeasures

Abstract: In recent research it turned out that Boolean verification of digital signatures in the context of WSSecurity is likely to fail: If parts of a SOAP message are signed and the signature verification applied to the whole document returns true, then nevertheless the document may have been significantly altered.In this paper, we provide a detailed analysis on the possible scenarios that enable these signature wrapping attacks. Derived from this analysis, we propose a new solution that uses a subset of XPath instea… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
24
0
3

Year Published

2009
2009
2022
2022

Publication Types

Select...
4
3
2

Relationship

2
7

Authors

Journals

citations
Cited by 45 publications
(29 citation statements)
references
References 13 publications
0
24
0
3
Order By: Relevance
“…However, also these extensions do not eliminate signature wrapping attacks completely, as discussed in [3].…”
Section: Related Workmentioning
confidence: 94%
See 1 more Smart Citation
“…However, also these extensions do not eliminate signature wrapping attacks completely, as discussed in [3].…”
Section: Related Workmentioning
confidence: 94%
“…We thus describe a solution based on an extension of Exclusive Canonicalization (which hopefully is implemented), and several other options to avoid this kind of attacks. However, one should keep in mind general defenses against wrapping attacks, as described in [1,2,3,4].…”
Section: Introductionmentioning
confidence: 99%
“…Though this is not impossible (cf. XML Signature Wrapping attacks [17], [18]), it poses severe restrictions to an attacker for properly crafting an attack message that can make use of the XML Signature over timestamp and SOAP body. Hence, having one XML Signature with n references tends to be the preferable approach.…”
Section: However In Terms Of Security Considerations For Web Servicementioning
confidence: 99%
“…XML wrapping involves manipulation of SOAP messages. A new element (i.e., the wrapper) is introduced into the SOAP Security header; the original message body is then moved under the wrapper and replaced by a bogus body containing an operation defined by the attacker [Gaj09,Gru09]. The original body can still be referenced and its signature verified, but the operation in the replacement body is executed instead.…”
Section: Identity and Access Managementmentioning
confidence: 99%