RUSTSEC-2022-0093: Double Public Key Signing Function Oracle Attack on ed25519-dalek
#158
Labels
wontfix
This will not be worked on
ed25519-dalek
#158
ed25519-dalek
1.0.1
>=2
Versions of
ed25519-dalek
prior to v2.0 model private and public keys asseparate types which can be assembled into a
Keypair
, and also provide APIsfor serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the
S
part of the signature,but not in the
R
value. An adversary could somehow use the signing function asan oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same
R
and only differ on theS
part.Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of
ed25519-dalek
do NOT allow a decoupledprivate/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: