Re: [Cfrg] Comments on the CPace proof and the CFRG PAKE selection process

Björn Haase <> Wed, 03 June 2020 17:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0245B3A0B72 for <>; Wed, 3 Jun 2020 10:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GD0ETq9sHDqs for <>; Wed, 3 Jun 2020 10:15:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 21B483A0B3C for <>; Wed, 3 Jun 2020 10:15:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=dbaedf251592; t=1591204512; bh=SZAVSPKaaXHJK3l9c2IAGDtSOk30P6ccG5ftZFIPb2M=; h=X-UI-Sender-Class:From:To:Subject:Date; b=VqXHjrnr+KDCt8hCOVCqSPZMhIBACygAf1yUSRg30oL54YAED1lO30lMrItwarkbt DOSoPnR/TY411dxrfwgFE6O+Bh8pYW1n78Qe8/Z2d1SDLDOuOUZEbuXsIDlS8QulIT X/bVxEMT6JoC2mvg4FU6mftq6Qbqw52yXx8peu6s=
X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9
Received: from [] ([]) by msvc-mesg-web101.server.lan (via HTTP); Wed, 3 Jun 2020 19:15:12 +0200
MIME-Version: 1.0
Message-ID: <trinity-6cea2880-383e-4fb7-a547-7328cfed1dd5-1591204512406@msvc-mesg-web101>
From: =?UTF-8?Q?Bj=C3=B6rn_Haase?= <>
To:, Michel Abdalla <>
Content-Type: text/html; charset=UTF-8
Importance: normal
Date: Wed, 3 Jun 2020 19:15:12 +0200
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-Provags-ID: V03:K1:v9NLyfic+37eJV31f2i9sSH2/XHkbUVYnPsViq07RuaLsMONQWGyxADLGIKbskNVRlDQp CsTfk8wMF3BgwC1hgxYT7SPo/8yJgjFllw33TrM1enD09K1wappRLIh/HXjnGD4526Hter9R/XCt POcbKieF/nvVhuaLgb4kU5uC1iJpqiwSGAZMe8xIxgT21H1Fi7wyhG0WagvrS3YTdDy61HPxLwna o3KH/TOmv6ix7NHZGY5LkOQhvpTmGx52sobDvMa2dFgjMtaH7CbtQsQjfOZziiWByixB6axyWmdS ng=
X-UI-Out-Filterresults: notjunk:1;V03:K0:Te1hm7sFU/Q=:LJ/iSKXS12p4t5cdlcZ46+ OMadaP1xPOOTqlEd8o0jut7Ma8H1ei8XP1tYK50IAucu05tIWB1Ysx58EtCyyD4TNd8tIjVH2 Q5JcxLfO/kFPZaKDLpH1It+Y50B9qPdP0eSOJSS8YEAk5XW1epnMMwCNJmrhQz4K6wTttbEiE 3KmzoXXFRYQO3IETlvwQ38ER5pYjsVCxal9fNQ7QZBaFWmar8v1l6gsXMZHAokFRgdL2dWaOm cncaRPeKH1mmpzVLeAv8lhF400tCUIaz/11k/KupF7/j0xDNhOO2tbuH3P41bLJewkOI8oZZw UkQ1EmT7fG/c4460IzKUsXG7XsXNuhohU5J2McOYkAeKqPraSwV3LCAc4Wu2hcLVeiVVb8MZF TW4nYxjGWfFIOwMl6XOi17qYDRfyfGkmATBW/zq3DKoBmWIXPaOUZ0J3sE6b3LK75wrXRXhAq BlH3Y8xDTO1mJTrEsBuYJWLtWiF7qj4/PxHWgeRejhTR18WgYrwgyPJBtG/OcDXDkpSnkblwN Byy3AMlnDZXd/0YXDZVOv4rIk1QciPcVNsQlFYtuGV/kuhGJ64VOrD22JiHhndtc2RVTxdsuI vxRTuLRhc+KTbkOcGrGj3bW8sTFmwQXR/7iIUYwiKzX697AW9zAigSbxWAcCZqxVNpqiSTv4K +tcbPNtVOOCrC15hYGyzZEoSlO/cN4/x7fskt/ELRP2xP4qqdAtLMHtU83w1aBI+Fg0N67l9Y DZoevh6o6TdFkebl+uBmzvaUMgT6hPaqQXTNBg==
Archived-At: <>
Subject: Re: [Cfrg] =?utf-8?q?Comments_on_the_CPace_proof_and_the_CFRG_PAKE_s?= =?utf-8?q?election_process?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Jun 2020 17:15:21 -0000

As I have Receiver a requests top give at least a preliminary short response before getting back top my office Equipment you will find a first feedback inline in the text below.

First let me also allow top clearify that some of the topics came up because the CPace construction aims at also adressing Implementation pitfalls and efficiency aspects from the very beginning which introduces additional complexity for the proofs.

Regarding the Point 1) , the reason for adding the transcripts is mainly related to the complexity of the ideal functionality. Without the transcripts the adversary needs to bei given the ability to "undo" a previous Interrupt query. Thus would have resulted in the need for an additional "undo" query for the ideal functionality, which we did not want to include. Note that in the "attack" that you sketch no harmful capability is given to the adversary. Only honest parties will authenticate and the adversary does mit learn anything. Even though the ID does mit have such a vulnerability.

Regarding point 2) there is no gap in the proofs because the sign is not required or assumed to be evaluated or transmitted by the protocol. The only reason for including it shows up in the context of legacy encoding conventions that facilitate Point verification since a square root calculation is made obsolete by a receiving party. Note that mandatorily adding the sign would have been easier from a proof Perspektive but would make the protocol more vulnerable from a Side channel perspective. X-coordinate only algorithms, e.g. for X25519 with a Montgomery ladder would not have been possible and possibly slower and more difficult to protect algorithms would have been necessary.

Regarding point 3) I will be responding more extensively. Note however, that your suggestion of adding the password to the Key derivation will considerably weaken the Side channel properties. Note that the ID of CPace carefully considers that the password must only enter at one single place since Power Analysis attacks on Hash primitives are particularly difficult to protect. Note that the GitHub paper is very Close to your recent findings regarding the relaxed ideal functionalities. Maybe you overlooked this final contribution to the CFRG process, because its not yet on the iacr eprints.

As you Note regarding point 4), the property of adaptive Security directly related to the way, the programmable RO for deriving the Generator is modelled. I agree that the way we treat the RO is highly idealized. This idealization gives the Simulator Access to the discrete Log and the idealization that Grants this Access is mandatory for adaptive corruptions.

Regarding perfect and weak forward Security, this property is directly related to presence of explicit Key confirmation. In the ideal functionality formulation this is tied to the availability of late Test Pwd queries. Thus aspects is considered in an Appendix in the current Version of the eprint 2018/286. The latest paper in GitHub only considers The protocol Variant without explicit confirmation that provides weak FS.

Regarding the insecurity of the CPace protocol variants I strongly disagree. I am also astonished that you give such a statement at this time without pointing out an actual vulnerability. The issues above we're alrrady consideres in the CFRG process openly or in my discussions with reviewers and Panel members.

Let me summarize that most of the topics that you brought up stem from CPaces Design Goals of also preventing Side channel and Implementation pitfalls.

Note that in my opinion These aspects might be of extremely high priority and worth beeing considered even if this adds complexity in the proofs .



Diese Nachricht wurde von meinem Android Mobiltelefon mit http://WEB.DE" rel="nofollow">WEB.DE Mail gesendet.
Am 02.06.20, 00:42 schrieb Michel Abdalla <>fr>:
Hi everybody,

Given that CPace has been selected as the balanced PAKE option, I believe it is important to make a few comments about its security as well as the CFRG PAKE selection process.  

1) Inclusion of the protocol transcript in the key derivation function

Although the latest RFC for CPace (" class="" rel="nofollow">link) includes the protocol transcript in the key derivation function (suggested by Bjoern Tackmann), the security analysis in the corresponding paper (" class="" rel="nofollow">link) does not clearly state the reasons for it. In particular, when examining the proof, the inclusion of the transcript during the computation of ISK has not been applied consistently throughout the paper and the analysis does not seem to make use of this fact.  

Here I would like to point out that this requirement is a hard one. Without it, the protocol would be insecure. To see why, just consider the following man-in-the-middle attack during an execution between a server and a client having the same password.

(a) When the server sends Y_a, the attacker forwards Y_a^2 = G^{2 y_a c_j} to the client
(b) When the client sends Y_b, the attacker forwards Y_b^2 = G^{2 y_b c_j} to the server
(c) The client and the server would compute the same ISK despite seeing different messages, since the key used to derive it would be the same: G^{2 y_a y_b c_j^2}.

2) Trivial malleability attacks

When introducing the protocol transcript in the key derivation function, the current RFC for CPace does not use the actual values of Y_a and Y_b to compute ISK. Instead, the input of the key derivation function uses strip_sign_information(Y_a) and strip_sign_information(Y_b).

One problem with this is that trivial modifications of the messages (for instance by changing Y_a to -Y_a) by a MITM attacker would not be detected by honest parties since the final key derivation does not properly bind the session keys to the transcript.

Although such an issue can be easily fixed by avoiding the use of strip_sign_information(), it clearly shows an important gap in the current proof.   

3) Reduction to SDH

The reduction to the SDH problem in the latest version of the Haase’s paper is still not given explicitly. Hence, right now, the security analysis only shows that the SDH is a necessary assumption but not necessarily sufficient.  Though such a reduction might be possible, I still don’t see exactly how it can be done so it would be nice if the Haase and Labrique could address this gap in the proof.  

In a separate paper currently available on ePrint (" class="" rel="nofollow">link), we provide proofs in the UC model for SPAKE2, TBPEKE, and SPEKE. Our results for TBPEKE and SPEKE can also be extended to CPace but only in the case where the key derivation includes the transcript of the communication (which is required) and the password (we may be able to remove this requirement with further analysis).

As stated in the paper, our proofs for SPAKE2 and TBPEKE rely on the gap versions of the CDH and SDH assumptions. In particular, the Decision Diffie-Hellman oracle is used throughout these proofs to maintain consistency of answers to RO queries, and that this is needed even to deal with sessions in which the adversary is passive: the reduction still needs to be able to consistently deal with the sessions where the attacker is active and the attacker may adaptively decide to launch an active attack after seeing one of the protocol messages. In the case of SPAKE2, removing the need of a gap assumption might be possible given the recent result by Shoup (" class="" rel="nofollow">link).  

4) Static versus adaptive UC security

Our proofs of security for SPAKE2, TBPEKE, and SPEKE in" class="" rel="nofollow"> only assume static corruptions and it would be interesting to extend them to deal with adaptive corruptions, but doing so does not seem straightforward.

The current security claim for CPace in" class="" rel="nofollow"> still claims adaptive security. Unfortunately, since the reductions to the SDH problem are not explicitly given, one cannot verify how corruptions can be handled during these reductions. Note that, when reducing to the SDH problem, the reduction would not know the discrete log of some of the values being exchanged and, hence, it might be hard to know how to properly answer adaptive corruption queries.

5) Perfect forward secrecy vs weak forward secrecy

The UC relaxations used in the proofs of security of CPace, TBPEKE, SPEKE, and SPAKE2 are not known to imply perfect forward secrecy without an additional key confirmation step. In particular, the notion of lazy-extraction UC PAKE in" class="" rel="nofollow"> is only known to imply weak forward secrecy. Interestingly, proving perfect forward secrecy without the key confirmation step seems to be significantly harder. In the case of SPAKE2, we were able to provide a game-based proof for it under gap CDH (see" class="" rel="nofollow">, but the reduction is not tight and requires an intermediate assumption previously used in the proof of SPAKE1. A similar result is currently not known for CPace, TBPEKE, and SPEKE.

6) Comment on the CFRG PAKE selection process

Since the selection process is now over and I no longer have a conflict of interest, I would like to end this email by commenting on the CFRG PAKE selection process.

On the one hand, the selection process highlighted several important security aspects for real-world PAKE schemes, such as side-channel resistance and quantum annoyance. The notion of quantum annoyance is actually quite interesting and something which we never considered when designing SPAKE2 back in 2005. Nevertheless, I also find it hard to argue that a protocol can satisfy it, since this property was never formally defined, let alone formally proved to hold for any of the candidates.

On the other hand, I was a bit surprised to see that concerns about security proofs were often ignored in the process. Among the 4 candidates for balanced PAKE, CPace seems to be the one for which nobody was ever able to verify its proofs. Yet, its theorems and strong security claims were mostly taken for granted because people seemed to believe that a correct proof for it could be given (me included) and this seemed to have played an important role in the process. However, what the different MITM attacks given above show is that the security of CPace is still not very well understood. In particular, the current version of CPace still lacks appropriate verifiable proofs and all the versions of the CPace scheme in" class="" rel="nofollow"> and TCHES are insecure.

As a result, moving forward, I would strongly recommend against taking security statements for granted if they cannot be verified. Moreover, I also believe that the issues with the security proof of CPace should be fully addressed before proceeding with any formal specification of the latter. 


PS: I would like to acknowledge the help of Manuel Barbosa with whom I discussed the security issues mentioned above.

_______________________________________________ Cfrg mailing list