Skip to content

Momentum-Safe/ed25519-unsafe-libs

BranchesTags
 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

76 Commits
ed25519-chalkias-exploit
ed25519-chalkias-exploit
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
dalek_api_misuse.jpg
dalek_api_misuse.jpg
 
 

Repository files navigation

ed25519-unsafe-libs

List of potentially unsafe ed25519 signature libraries that allow a public api where secret and public key can be provided independently as signing function inputs. Misuse of these public apis can result to private key exposure.

Μost of the repositories in our analysis are enlisted in IANIX :: Things that use Ed25519.

Number of impacted libraries: 48
Number of libraries that fixed the issue after the announcement: 6
last updated: Aug 28, 2022

Proof of Concept implementations that demonstrate this potential exploit:

News and social network coverage of this attack

  • The Daily Swig "Dozens of cryptography libraries vulnerable to private key theft" (June 28, 2022)
  • Risky Biz News "New crypto vulnerability: Tens of cryptography libraries have misimplemented the Ed25519 digital signature algorithm" (June 28, 2022)
  • SafeHeron blogpost "Analysis on Ed25519 Use Risks: Your Wallet Private Key Can Be Stolen" (June 17, 2022)
  • kryptera.se "Vulnerability in most ed25519 libraries" (in Swedish) (June 29, 2022)
  • Difesa e Sicurezza & Yoroi "Librerie crittografiche ed25519 potenzialmente non sicure" (in Italian) (July 1 & June 29, 2022)
  • Medium post by Prof Bill Buchanan OBE "Ed25519 is Great, But ..." (July 1, 2022)
  • Reddit r/crypto (best post of the month - June 18, 2022)
  • Reddit r/cryptography (June 17, 2022)
  • Interesting tweets:
    • tweet 1 (by Kostas Kryptos - "The original 26 vulnerable libs")
    • tweet 2 (by Kostas Kryptos - "Aftermath of the 40 vulnerable libs")
    • tweet 3 (by Catalin Cimpanu - "40 cryptography libraries are impacted by same Ed25519 misimplementation")
    • tweet 4 (by Kenny Paterson - "Potential for widespread EdDSA private key recovery, cf. http://kopenpgp.com where same vector exploited in OpenPGP libs")
    • tweet 5 (by Steven Galbraith - "A hazard for deterministic signatures: better check it is the correct public key!")
    • tweet 6 (by Riyaz Faizullabhoy - "If you’re using EdDSA in prod please take a look")
    • tweet 7 (by Bart Preneel - "Reminder that implementing cryptographic algorithms securely and correctly is hard").

What is the issue?

Note that normally and according to the related rfc8032, EdDSA signatures are deterministic, and thus for the same input message to be signed, a unique signature output that includes two elements, a curve point R and a scalar S, is returned.

An algorithmic detail is that that signer's public key is invloved in the deterministic computation of the S part of the signature only, but not in the R value. The latter implies that if an adversary could somehow use the signing function as an Oracle (that expects arbitrary public keys as inputs), then it is possible that for the same message one can get two signatures sharing the same R and only differ on the S part. Unfortunately, when this happens, one can easily extract the private key; this StackOverflow post post explains why this is feasible.

That said, public apis should NOT allow a decoupled private/public key-pair as signing input. To circumvent that, many implementations store the public key along with the private key (or seed) and consider the whole keypair as the secret OR they always re-derive the public key inside the signing function. Unfortunately, a large number of existing libraries fail to address this issue by allowing arbitrary public keys as inputs without checking if the input public key corresponds to the input private key.

Of course, this does not mean that all applications with dependencies to these libraries are prone to key exposure attacks; actually, most are probably safe due to usually not publicly exposing the affected api to their users and coupling their pub/priv key pair just before the sign invocation. On the other hand, even when these apis are not exposed, there are applications with different TCB threat model strategies on how the private and public keys are managed and stored. That said, to prevent this attack, developers should also enforce an integrity protection protocol for the public keys as well.

Here, we enlist some of the affected libraries along with the related code-references.

Ed25519 api misuse resulting to key extraction Fig 1. An example api misuse in the ed25519-dalek Rust crate.

Affected libraries

Fixed libraries

About

List of unsafe ed25519 signature libs

Resources

Readme

License

MIT license
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages

  • Rust 100.0%