Impact
The verifyWithMessage
method of tEnvoyNaClSigningKey
always returns true
for any signature of a SHA-512 hash matching the SHA-512 hash of the message even if the signature is invalid.
Patches
Upgrade to v7.0.3
immediately to resolve this issue. Since the vulnerability lies within the verification method, the previous signatures are still valid. We highly recommend reverifying any signatures that were previously verified with the vulnerable verifyWithMessage
method.
Workarounds
In tenvoy.js
under the verifyWithMessage
method definition within the tEnvoyNaClSigningKey
class, ensure that the return statement call to this.verify
ends in .verified
. For example, the return statement should start with return this.verify(signed, password).verified &&
instead of return this.verify(signed, password) &&
.
For more information
If you have any questions or comments about this advisory:
Impact
The
verifyWithMessage
method oftEnvoyNaClSigningKey
always returnstrue
for any signature of a SHA-512 hash matching the SHA-512 hash of the message even if the signature is invalid.Patches
Upgrade to
v7.0.3
immediately to resolve this issue. Since the vulnerability lies within the verification method, the previous signatures are still valid. We highly recommend reverifying any signatures that were previously verified with the vulnerableverifyWithMessage
method.Workarounds
In
tenvoy.js
under theverifyWithMessage
method definition within thetEnvoyNaClSigningKey
class, ensure that the return statement call tothis.verify
ends in.verified
. For example, the return statement should start withreturn this.verify(signed, password).verified &&
instead ofreturn this.verify(signed, password) &&
.For more information
If you have any questions or comments about this advisory: