by Kastro
Paper/Archive/CVE-2021-32685

CVE-2021-32685

TogaTech tEnvoy — Improper Verification of Cryptographic Signature in tenvoy

EPSS 0.7%CVSS 9.8
critical.is priorityof 100
40
CVSS 9.8 (CNA, NVD agree)9.8 / 10 × 3029.4Not in CISA KEV+300.0EPSS percentile 51.5.515 × 2010.3No public exploit+100.0SSVC exploitation: unknown+100.0
Description · from the CVE record

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`.

Affected

ProductAffectedFixed inSource
tEnvoy< 7.0.3–CNA

Scores by source

GitHub_M (CNA)9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

refgithub.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36mrefgithub.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686brefgithub.com/TogaTech/tEnvoy/releases/tag/v7.0.3