CVE-2021-32685 Improper Verification of Cryptographic Signature in tenvoy
Attackers can bypass cryptographic signature verification in tEnvoy, allowing them to forge valid signatures for arbitrary messages.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-32685?
CVE-2021-32685 is a critical vulnerability in TogaTech tEnvoy, published on 16 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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`.
Weakness: CWE-347
Which versions are affected by CVE-2021-32685?
2 open source packages ship an affected version, including tenvoy. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tenvoy npm | All versions | 7.0.3 |
tenvoy npm | All versions | 7.0.3 |
Products include Togatech Tenvoy.
How do I fix CVE-2021-32685?
Upgrade tenvoy to 7.0.3 or later.
Is CVE-2021-32685 being exploited?
There is no known exploitation of CVE-2021-32685 in the wild and no public exploit code.
Sources
Also known as GHSA-7r96-8g3x-g36m.