GHSA-7r96-8g3x-g36m

Suggest an improvement
Source
https://github.com/advisories/GHSA-7r96-8g3x-g36m
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/06/GHSA-7r96-8g3x-g36m/GHSA-7r96-8g3x-g36m.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-7r96-8g3x-g36m
Aliases
Published
2021-06-28T17:16:56Z
Modified
2026-07-08T06:27:47Z
Severity
  • 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
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:

Database specific
{
    "cwe_ids":  [
        "CWE-347"
    ],
    "github_reviewed":  true,
    "github_reviewed_at":  "2021-06-16T20:14:25Z",
    "nvd_published_at":  null,
    "severity":  "CRITICAL"
}
References

Affected packages

npm / tenvoy

Package

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
7.0.3

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/06/GHSA-7r96-8g3x-g36m/GHSA-7r96-8g3x-g36m.json"