##### Pierrick Gaudry (CNRS, Inria, Université de Lorraine)

##### 8 August 2019

**Update added on August 23**: an attack on the revised encryption scheme has been found by Alexander Golovnev, from Harvard! Please read his article for the details on how it works.

**Update added on August 22**: the code on Github has been updated. The multi-level ElGamal has disappeared and the key is now 1024 bit long. There has been some more deep change in the protocol as well, since now the decryption is no longer done by a smart-contract executed in the blockchain. I have been asking for a proper documentation of the protocol, but didn’t get any (yet?). Therefore, it is hard to tell the consequences of these changes, but I consider it quite dangerous to do so many modifications only a few weeks before the real election. It would be wise to acknowledge that the system is not yet ready for production and to postpone its use.

**Update on August 16**: small change in the script to make it more robust.

**Update added on August 13**: after we contacted the people in charge in Russia before making this note public, they made a reply on Iuliia Krivonosova’s blog. They acknowledge that the keys are too small and they plan to upgrade to 1024 bits. They didn’t provide a proper specification of the system yet.

### Context

[ * Disclaimer: most of the context information here relies on secondary sources or automatic translation of texts written in Russian. There is a possibility of misunderstanding by the author.* ]

In September 2019 (one month in the future, at the date of the writing of this note), there will be elections in Moscow for the representatives at the Parliament of the city (the Moscow City Douma). During this election, up to half a million of voters will be allowed to use internet voting. The voting system that will be used has been the subject of a public test at the end of July, during which some of the source code was made public on Github [1].

Although we did not find (yet?) a public specification of the protocol in English, we understand that it uses the Ethereum blockchain, with its smart contract capabilities.

During the public test, the public code was updated every day, proposing new public keys and new encrypted data, and revealing the private keys and the original data of the day before. According to the README.md file, the goal was to decrypt the data in less than 12 hours, since this will be the duration of the election to be held in September.

### Result

We will show in this note that the encryption scheme used in this part of the code is completely insecure. It can be broken in about 20 minutes using a standard personal computer, and using only free software that is publicly available. More precisely, it is possible to compute the private keys from the public keys. Once these are known, any encrypted data can be decrypted as quickly as they are created.

Without having read the protocol, it is hard to tell precisely the consequences, because, although we believe that this weak encryption scheme is used to encrypt the ballots, it is unclear how easy it is for an attacker to have the correspondence between the ballots and the voters. In the worst case scenario, the votes of all the voters using this system would be revealed to anyone as soon as they cast their vote.

### The encryption scheme

We describe here what we have understood from the directory

smart-contracts/packages/crypto-lib/src/

of the public code [1].

The encryption is based on the ElGamal scheme. For a cyclic group G of generator g, given a public key h and a message m, the scheme produces a pair Enc_{g,h}(m) = [a, b]. And knowing the secret key x (i.e. the discrete logarithm of h relative to g), it is possible to decrypt: Dec_{g,x}(a,b) = m. The description in Wikipedia [2] is what is implemented, so we refer to it for further details. Let us just mention that if one part of the ciphertext (a or b) is missing, then even knowing the secret key, there is no way to decrypt and get the original message.

In the Moscow system, things are a bit more complicated, because a variant using 3 levels of encryption is implemented. Let G1, G2, G3, be three cyclic groups of generators g1, g2, g3. There are three public keys h1, h2, h3, one for each group. In order to encrypt a message m, they first compute the following:

- [ a1, b1 ] := Enc_{g1,h1}(m)
- [ a2, b2 ] := Enc_{g2,h2}(a1)
- [ a3, b3 ] := Enc_{g3,h3}(a2)

and then the ciphertext is the quadruple [b1, b2, a3, b3]. The values a1 and a2 are forgotten, but someone knowing the private keys x1, x2, x3 corresponding to h1, h2, h3, will be able to deduce m as follows:

- a2 := Dec_{g3,x3}(a3, b3)
- a1 := Dec_{g2,x2}(a2, b2)
- m := Dec_{g1,x1){a1, b1)

The purpose of this multi-level encryption is not known to us. It can not be security, because this will be only marginally more secure that using only the group which is the most secure.

The main problem is due to the choice of G1, G2, G3. In [1], in the encryption-keys/keys subdirectory, there is a file called public-key.json that contains a description of them. They are multiplicative groups of finite fields of prime orders p1, p2, p3, each of them being Sophie Germain primes. There is nothing wrong with this apart from the sizes of p1, p2, p3, which are all less than 256-bit long. This is way, way too short to guarantee any security.

We will see below that discrete logarithms in such a small setting can be computed in a matter of minutes, thus revealing the secret keys, and then all the encrypted data becomes easy to decrypt.

Before going to this, we mention quickly another mistake in the design that could in itself have led to devastating attacks. The generators that are given in public-key.json are generators of the whole multiplicative group. However, due to the Chinese remainder theorem, it is a good practice to use a generator of prime order. In the present case, the generators will have their order divisible by 2, and therefore there is a huge risk that one bit of information leaks from a ciphertext. In a context like e-voting where a ballot can have a very simple form, this bit of information could reveal a lot of the vote (or even all of it in the case of a yes/no question). In principle, we would have had to investigate more in this direction. But due to the main attack that is much easier and far more powerful, we keep this as a remark.

### Computing discrete logarithms

We now explain the state of the art of computing discrete logarithms in finite fields.

The best known algorithm for this task is the Number Field Sieve that was invented in the early 90’s [3]. It is a complicated algorithm that uses heavy notions of number theory. Also, it is not suitable for computing discrete logarithms in very small finite fields, for which better algorithms are known. However, when the prime p has more than a few dozens of digits, like the primes we are interested in, it becomes clearly the best.

For our attack, we used CADO-NFS [4] which is a free software implementation of the Number Field Sieve, the author of this note being one of the major developers of this piece of software. The last official release is rather old, so we used the development version, that is available from the public git repository.

CADO-NFS takes as input p and h and computes the discrete logarithm of h in GF(p) relative to an arbitrary generator. In order to get the discrete logarithm of h relative to the given generator g, one has to run CADO-NFS again to get the logarithm of g, so that we can divide those two values (this is similar to what we do to compute the log in base 2 of a number when the pocket calculator provides only the log in base e). Fortunately, many parts of the computation can be shared between those two runs, and CADO-NFS does indeed share them automatically.

Another complication is due to the fact that CADO-NFS assumes that we are in the prime order setting (as explained above, this should be what people do!), while here the order is twice a prime. This means that we have some additional easy operations to do in order to deduce the private keys corresponding to what is expected in the Moscow system.

All of these operations to be done once CADO-NFS has outputted its results are elementary number theory (just modular arithmetic) and take no time. This is included in the shell script given in Appendix, for reproducibility.

Once everything is compiled, we measured the time to compute each of the 3 private keys, corresponding to the last public keys published in the repo [1] on August 1st. The computation was done on a personal computer equipped with a 4-core Intel i5-4590 processor at 3.3 GHz and 16 GB of RAM. It is running a standard Debian distribution.

The running times to retrieve the private keys are as follows:

key number | time |

1 | 425 sec |

2 | 507 sec |

3 | 314 sec |

Note that the variation in the running time from one key to the other is not unusual for computations with moderately small primes.

Of course, for a real attack, the three keys can be computed on 3 machines in parallel. CADO-NFS also has some parallelism capabilities so that machines with more cores can reduce the time for a single key. However, there is some limit to it with the current implementation. For instance, the private key number 1 could be retrieved in 160 seconds on a machine with 64 cores.

### Breaking the scheme

Now that we have everything in place, the scenario of the attack is the following. Before the day of elections, machines are prepared with everything compiled and tested. As soon as the election opens, the public keys must be available, so that voters can encrypt their ballot. Then with the strategy we have just described and explicitly applied in the shell script given in Appendix, the attacker can retrieve all the private keys in less than 10 minutes using 3 standard personal computers, or even less if they have access to a more powerful machine. They can then decrypt all the data that is supposed to be secured by this encryption. In particular, if the ballots are protected with this, they must be considered as being in cleartext as soon as they are cast.

### Remaining questions

- Why such small keys?

A possible explanation is a confusion with the key size that can be used when using elliptic curves for which the Number Field Sieve algorithm does not apply.

Another less excusable but still possible explanation might be related to the use of the Ethereum blockchain. In the Solidity programming language that is used to write smart contracts, the bit size of the largest supported integers is 256. Maybe the authors did not want to write a multiprecision arithmetic library that would have been required to deal with larger key sizes. This hypothesis is supported by frequent tests in the source code, checking that the big integers they manipulate are not bigger than SOLIDITY_MAX_INT.

- Where does the multi-level ElGamal comes from?

This is a mystery. The only possible explanation we can think of is that the designers thought this would compensate for the too small key sizes of the primes involved. But 3 primes of 256 bits are really not the same as one prime of 768 bits.

- Are the ballots really encrypted with this scheme?

From the source code, in particular in the subdirectory named smart-contracts/packages/voting-lib/src/contracts, our guess is that yes. However, reading a proper specification of the voting scheme would be the only way to know.

- Is there an easy fix?

In principle, yes: increase the key size. However, if the hypothesis that writing a multiprecision library for Solidity is a problem appears to be correct, there is no easy workaround. Using elliptic curves is probably a good idea, but again this is not a change that can be done in just a few hours of coding.

Maybe there is an easier fix by changing the protocol, so that the smart contracts do not compute anything with the encrypted ballots.

### Acknowledgements

Thanks to Iuliia Krivonosova and Robert Krimmer, for sharing information about the Moscow internet voting. In particular Iuliia’s blog post was quite useful.

### References

[1] Public source code of the Moscow internet voting system.

https://github.com/moscow-technologies/blockchain-voting.git

[2] Wikipedia page « ElGamal encryption »

https://en.wikipedia.org/wiki/ElGamal_encryption

[3] The development of the Number Field Sieve.

A.K. Lenstra and H.W. Lenstra Jr. (Eds)

Lecture notes in mathematics vol 1554.

Springer-Verlag 1993

[4] CADO-NFS, An Implementation of the Number Field Sieve Algorithm

The CADO-NFS Development Team.

Development version fdae0f9f382c, August 2019.

http://cado-nfs.gforge.inria.fr/

### Appendix: a shell script for the attack

*[ This script can be downloaded from this link to avoid issues with html encoding. ]*

## These are commands to be run on a Linux machine (Debian or Ubuntu).

## The main workhorse for the discrete logarithm computations is CADO-NFS,

## and we use GP-Pari as a 'pocket calculator' for modular arithmetic.

```
```# install some packages

sudo apt install pari-gp jq

sudo apt install libgmp3-dev gcc g++ cmake libhwloc-dev

alias gpnoc="gp -q --default colors=\"no\""

# download and compile cado-nfs

cd /tmp

git clone https://scm.gforge.inria.fr/anonscm/git/cado-nfs/cado-nfs.git

cd cado-nfs

# A previous version of this script was using version fdae0f9f382 of

# CADO-NFS, but this was not robust.

git checkout 6b3746a2ec27 # version of 16/08

make cmake

make -j 4

# download blockchain-voting and extract public keys

cd /tmp

git clone https://github.com/moscow-technologies/blockchain-voting.git

cd blockchain-voting

git checkout d70986b2c4da # most recent version at the time of writing

cd /tmp

# loop on the 3 public keys; could be done in parallel on 3 machines.

for i in {0,1,2}; do

start=`date +%s`

# extract the public key information

p=`jq .modulos[$i] /tmp/blockchain-voting/encryption-keys/keys/public-key.json | tr -d \"`

g=`jq .generators[$i] /tmp/blockchain-voting/encryption-keys/keys/public-key.json | tr -d \"`

h=`jq .publicKeys[$i] /tmp/blockchain-voting/encryption-keys/keys/public-key.json | tr -d \"`

ell=`echo "($p-1)/2" | gpnoc`

# run cado-nfs to get log of h (takes a few minutes)

wdir=`mktemp -d /tmp/cadorunXXXXXX`

log_h=`/tmp/cado-nfs/cado-nfs.py -dlp -ell $ell workdir=$wdir target=$h $p`

# run again to get log of generator (faster, since it reuses precomputed data)

log_g=`/tmp/cado-nfs/cado-nfs.py $wdir/p75.parameters_snapshot.0 target=$g`

# deduce private key

x=`gpnoc <<EOF

xell=lift(Mod($log_h,$ell)/Mod($log_g,$ell)); half=lift(1/Mod(2,$ell));

x0=lift(Mod(2*half*xell, 2*$ell)); h0=lift(Mod($g,$p)^x0);

if (h0 != $h, x0=lift(Mod(2*half*xell+$ell, 2*$ell)));

x0

EOF`

`stop=`date +%s``

echo "Private key number $((i+1)) is $x, computed in $((stop-start)) seconds."

done