Most recent entries from all

cnvd-2021-44985

EUVD-2026-28070

fkie_cve-2021-32685

tEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-512 hash matching the SHA-512 hash of the message even if the signature was invalid. This issue is patched in version 7.0.3. As a workaround: In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.

GHSA-7r96-8g3x-g36m — Improper Verification of Cryptographic Signature

Affected: npm: tenvoy

### 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: * Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)

Most recent entries from all

cnvd-2021-44985

EUVD-2026-28070

fkie_cve-2021-32685

GHSA-7r96-8g3x-g36m — Improper Verification of Cryptographic Signature

gsd-2021-32685