MQV has some weaknesses that were fixed by HMQV in 2005.[1] A few articles[2][3] offered alternative viewpoints. It is now known that HMQV is vulnerable to a KCI attack when ephemeral public keys are not validated

ECMQV has been dropped from the National Security Agency's Suite B set of cryptographic standards.

Contents

Alice has a key pair (A,a){\displaystyle (A,a)} with A{\displaystyle A} her public key and a{\displaystyle a} her private key and Bob has the key pair (B,b){\displaystyle (B,b)} with B{\displaystyle B} his public key and b{\displaystyle b} his private key.

In the following R¯{\displaystyle {\bar {R}}} has the following meaning. Let R=(x,y){\displaystyle R=(x,y)} be a point on an elliptic curve. Then R¯=(xmod2L)+2L{\displaystyle {\bar {R}}=(x\,{\bmod {\,}}2^{L})+2^{L}} where L=⌈⌊log2⁡n⌋+12⌉{\displaystyle L=\left\lceil {\frac {\lfloor \log _{2}n\rfloor +1}{2}}\right\rceil } and n{\displaystyle n} is the order of the used generator point P{\displaystyle P}. So R¯{\displaystyle {\bar {R}}} are the first L bits of the first coordinate of R{\displaystyle R}.

Step

Operation

1

Alice generates a key pair (X,x){\displaystyle (X,x)} by generating randomly x{\displaystyle x} and calculating X=xP{\displaystyle X=xP} with P{\displaystyle P} a point on an elliptic curve.

2

Bob generates a key pair (Y,y){\displaystyle (Y,y)} in the same way as Alice.

The original MQV protocol does not include user identities of the communicating parties in the key exchange flows. User identities are only included in the subsequent explicit key confirmation process. However, explicit key confirmation is optional in MQV (and in the IEEE P1363 specification). In 2001, Kaliski presented an unknown key-share attack that exploited the missing identities in the MQV key exchange protocol.[4] The attack works against implicitly authenticated MQV that does not have explicit key confirmation. In this attack, the user establishes a session key with another user but is tricked into believing that he shares the key with a different user. In 2006, Menezes and Ustaoglu proposed to address this attack by including user identities in the key derivation function at the end of the MQV key exchange.[5] The explicit key confirmation process remains optional.

In 2005, Krawczyk proposed a hash variant of MQV, called HMQV.[1] The HMQV protocol was designed to address Kaliski's attack (without mandating explicit key confirmation), with the additional goals of achieving provable security and better efficiency. HMQV made three changes to MQV:

Including the user identities in the key exchange flows: more specifically, letting X¯=H(X,B){\displaystyle {\bar {X}}=H(X,B)} and Y¯=H(Y,A){\displaystyle {\bar {Y}}=H(Y,A)} where A{\displaystyle A} and B{\displaystyle B} are identities of Alice and Bob respectively.

Removing the mandatory requirement in MQV that a Certificate Authority (CA) must verify the proof-of-possession of the user's private key during the public key registration. In HMQV, the CA merely needs to check the submitted public key is not 0 or 1.

Removing the mandatory requirement in MQV that a user must verify whether the received ephemeral public key is a valid public key (known as public key validation). In HMQV, a user merely needs to check the received ephemeral public key is not 0 or 1.

HMQV claims to be superior to MQV in performance because it dispenses with the operations in 2) and 3) above, which are mandatory in MQV. The HMQV paper provides "formal security proofs" to support that dispensing with these operations is safe.

In 2005, Menezes first presented a small subgroup confinement attack against HMQV.[6] This attack exploits the exact missing of public key validations in 2) and 3). It shows that when engaged with an active attacker, the HMQV protocol leaks information about the user's long-term private key, and depending on the underlying cryptographic group setting, the entire private key may be recovered by the attacker. Menezes proposed to address this attack by at least mandating public key validations in 2) and 3).

In 2006, in response to Menezes' attack, Krawczyk revised HMQV in the submission to IEEE P1363 (included in the IEEE P1363 D1-pre draft). However, instead of validating the long-term and ephemeral public keys in 2) and 3) respectively as two separate operations, Krawczyk proposed to validate them together in one combined operation during the key exchange process. This saves cost. With the combined public key validation in place, Menezes' attack is prevented. The revised HMQV can still claim to be more efficient than MQV.

In 2010, Hao presented two attacks on the revised HMQV (as specified in the IEEE P1363 D1-pre draft).[7] The first attack exploits the fact that HMQV allows any data string other than 0 and 1 to be registered as a long-term public key. Hence, a small subgroup element is allowed to be registered as a "public key". With the knowledge of this "public key", a user is able to pass all verification steps in HMQV and is fully "authenticated" in the end. This contradicts the common understanding that "authentication" in an authenticated key exchange protocol is defined based on proving the knowledge of a private key. In this case, the user is "authenticated" but without having a private key (in fact, the private key does not exist). This issue is not applicable to MQV. The second attack exploits the self-communication mode, which is explicitly supported in HMQV to allow a user to communicate with himself using the same public key certificate. In this mode, HMQV is shown to be vulnerable to an unknown key-share attack. To address the first attack, Hao proposed to perform public key validations in 2) and 3) separately, as initially suggested by Menezes. However, this change will diminish the efficiency advantages of HMQV over MQV. To address the second attack, Hao proposed to include additional identities to distinguish copies of self, or to disable the self-communication mode.

Hao's two attacks were discussed by members of the IEEE P1363 working group in 2010. However, there was no consensus on how HMQV should be revised. As a result, the HMQV specification in the IEEE P1363 D1-pre draft was unchanged, but the standardisation of HMQV in IEEE P1363 has stopped progressing since.