Detailed Information on Publication Record
2020
Fooling primality tests on smartcards
SEDLÁČEK, Vladimír, Ján JANČÁR and Petr ŠVENDABasic information
Original name
Fooling primality tests on smartcards
Authors
SEDLÁČEK, Vladimír (203 Czech Republic, guarantor, belonging to the institution), Ján JANČÁR (703 Slovakia, belonging to the institution) and Petr ŠVENDA (203 Czech Republic, belonging to the institution)
Edition
Švýcarsko, 25th European Symposium on Research in Computer Security (ESORICS) 2020, p. 209-229, 21 pp. 2020
Publisher
Springer
Other information
Language
English
Type of outcome
Stať ve sborníku
Field of Study
10201 Computer sciences, information science, bioinformatics
Confidentiality degree
není předmětem státního či obchodního tajemství
Publication form
printed version "print"
References:
Impact factor
Impact factor: 0.402 in 2005
RIV identification code
RIV/00216224:14330/20:00114216
Organization unit
Faculty of Informatics
ISBN
978-3-030-59012-3
ISSN
UT WoS
001229989600011
Keywords in English
ECC; primality; pseudoprimes; smartcards
Tags
International impact, Reviewed
Změněno: 25/10/2024 16:13, Mgr. Natálie Hílek
Abstract
V originále
We analyse whether the smartcards of the JavaCard platform correctly validate primality of domain parameters. The work is inspired by Albrecht et al. (Prime and Prejudice) [1], where the authors analysed many open-source libraries and constructed pseudoprimes fooling the primality testing functions. However, in the case of smartcards, often there is no way to invoke the primality test directly, so we trigger it by replacing (EC)DSA and (EC)DH prime domain parameters by adversarial composites. Such a replacement results in vulnerability to Pohlig-Hellman [30] style attacks, leading to private key recovery. Out of nine smartcards (produced by five major manufacturers) we tested (See https://crocs.fi.muni.cz/papers/primality_esorics20 for more information), all but one have no primality test in parameter validation. As the JavaCard platform provides no public primality testing API, the problem cannot be fixed by an extra parameter check, making it difficult to mitigate in already deployed smartcards.
Links
GA20-03426S, research and development project |
| ||
MUNI/C/1701/2018, interní kód MU |
|