Advisory

GHSA-7r96-8g3x-g36m

Also known as: CVE-2021-32685

Summary

Improper Verification of Cryptographic Signature

Details

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:

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2021-06-28 17:16 UTC
Modified
2026-07-08 06:27 UTC

Affected packages and fixes

tenvoy

npm · All systems

Affected

  • introduced 0, fixed 7.0.3 (semver)

Fixed versions

7.0.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences