Approved changes feed: RSS · Atom
cpe:2.3:a:togatech:tenvoy:*:*:*:*:*:node.js:*:*part: a version: * update: *
| Vendor | Togatech (2a444cad-9636-5aaf-ba04-8476511bcc78) |
|---|---|
| Product | Tenvoy (fda7ca55-d0e2-51eb-b010-189945c29a17) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-32685 |
vulnerable | 2026-06-08 05:32:07.836825 |
Improper Verification of Cryptographic Signature in tenvoy
CRITICAL (9.8)
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`.
Published: 2021-06-16T00:25:11.000Z
Updated: 2024-08-03T23:25:31.108Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.