CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2021

CVE-2021-32685
Npm vulnerability

### 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: * Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Npm. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Npm runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.