2010
DOI: 10.1007/978-3-642-14577-3_22
|View full text |Cite
|
Sign up to set email alerts
|

PKI Layer Cake: New Collision Attacks against the Global X.509 Infrastructure

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
25
0

Year Published

2010
2010
2024
2024

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 37 publications
(27 citation statements)
references
References 5 publications
0
25
0
Order By: Relevance
“…In contrast, we are not interested in the cognitive aspects, and shall make the minimum possible assumptions about the user by defining a non-deterministic one. Kaminsky et al [18] point out that a subject name in an X.509 certificate can be easily misinterpreted by browsers because of lack of standardisation, which often invites ambiguity. To confirm this, a recent update of the X.509 standard [19] provides some clarifications, which, however, do not impact our work.…”
Section: Related Workmentioning
confidence: 99%
“…In contrast, we are not interested in the cognitive aspects, and shall make the minimum possible assumptions about the user by defining a non-deterministic one. Kaminsky et al [18] point out that a subject name in an X.509 certificate can be easily misinterpreted by browsers because of lack of standardisation, which often invites ambiguity. To confirm this, a recent update of the X.509 standard [19] provides some clarifications, which, however, do not impact our work.…”
Section: Related Workmentioning
confidence: 99%
“…It also harkens back to the classic work on evading intrusion detection and prevention systems (IDS/IPS) [16,23] that exploited differences in network streams reassembly by the attack targets and the IDS/IPS protecting them-which have since been generalized as parser differential attacks [19,25].…”
Section: Previous Workmentioning
confidence: 99%
“…When using a name like bank.comøevil.com, some CAs only validated that the registering user owns evil.com. However, some browsers (e.g., Firefox [30]) ignored everything following the NUL character and accepted the certificate for bank.com [21,25]. This bug has been fixed on both browser and CA side.…”
Section: Faults In Ca Processesmentioning
confidence: 99%