2006
DOI: 10.1007/11745853_25
|View full text |Cite
|
Sign up to set email alerts
|

Security Analysis of KEA Authenticated Key Exchange Protocol

Abstract: Abstract. KEA is a Diffie-Hellman based key-exchange protocol developed by NSA which provides mutual authentication for the parties. It became publicly available in 1998 and since then it was neither attacked nor proved to be secure. We analyze the security of KEA and find that the original protocol is susceptible to a class of attacks. On the positive side, we present a simple modification of the protocol which makes KEA secure. We prove that the modified protocol, called KEA+, satisfies the strongest securit… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
68
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 65 publications
(68 citation statements)
references
References 15 publications
0
68
0
Order By: Relevance
“…Lauter and Mityagin [33] produced the KEA+ protocol from the KEA protocol and Protocol 4 in [7] by incorporating the identifiers of the user and its peer in the session key computation to prevent UKS attacks; however, a similar UKS attack first identified in the current paper still works on the KEA+ protocol. This attack involves (a) a type of impersonation during key registration [44, p. 3] as it requires the adversary to successfully impersonate a user to the CA who then issues a certificate containing the user's identifier, but the adversary's valid public key, and (b) impersonation of that user during the key exchange phase.…”
Section: Capturing Attacksmentioning
confidence: 99%
“…Lauter and Mityagin [33] produced the KEA+ protocol from the KEA protocol and Protocol 4 in [7] by incorporating the identifiers of the user and its peer in the session key computation to prevent UKS attacks; however, a similar UKS attack first identified in the current paper still works on the KEA+ protocol. This attack involves (a) a type of impersonation during key registration [44, p. 3] as it requires the adversary to successfully impersonate a user to the CA who then issues a certificate containing the user's identifier, but the adversary's valid public key, and (b) impersonation of that user during the key exchange phase.…”
Section: Capturing Attacksmentioning
confidence: 99%
“…Yet attacks reported in [13] and [14] show that in both protocols, an attacker is able to disclose the user's private key. In the second requirement 5 , we use "full" to distinguish it from the "half" forward secrecy, which only allows one user's private key to be revealed (e.g., KEA+ [9]). In the past literature it is common to add "perfect" before "forward secrecy" [7], [9], [11].…”
Section: Security Analysismentioning
confidence: 99%
“…In the second requirement 5 , we use "full" to distinguish it from the "half" forward secrecy, which only allows one user's private key to be revealed (e.g., KEA+ [9]). In the past literature it is common to add "perfect" before "forward secrecy" [7], [9], [11]. However, we drop "perfect" here because it has no concrete meaning [10], [20].…”
Section: Security Analysismentioning
confidence: 99%
“…NAXOS builds on earlier ideas from the KEA and KEA+ protocols [15,16]. The purpose of the NAXOS protocol is to establish a shared symmetric key between two parties.…”
Section: H1 H2mentioning
confidence: 99%
“…In [16], the KEA+ protocol is proven correct in the CK model from [5]. KEA+ can be viewed as a predecessor of the NAXOS protocol, and uses a similar setup.…”
Section: The Kea Kea+ and Kea+c Protocolsmentioning
confidence: 99%