Vulnerability in tenvoy (CVE-2021-32685)
Summary
Vulnerability in tenvoy (CVE-2021-32685). Successful exploitation can lead to full system takeover. Exploitable via verifyWithMessage. Mitigation: upgrade to 7.0.3 or later.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32685 has been found in tenvoy.
Attackers can target a specific entry point like verifyWithMessage over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade tenvoy to 7.0.3 or later.
If unsure, ask your IT team or search "tenvoy CVE-2021-32685" on the vendor's site.
CVE-2021-32685 (tenvoy) — CWE-347
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: verifyWithMessage / tEnvoyNaClSigningKey / true / tenvoy.js
Patched: 7.0.3 — apply immediately
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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in tenvoy. Attackers reach the vulnerable code path via verifyWithMessage without authentication.
Check the vendor advisory for the affected versions of tenvoy. Attack surface: verifyWithMessage / tEnvoyNaClSigningKey / true / tenvoy.js.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 7.0.3.
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.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tenvoy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tenvoy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tenvoyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`.パッチが適用されるまでの応急処置として、In
tenvoy.jsunder theverifyWithMessagemethod definition within thetEnvoyNaClSigningKeyclass, ensure that the return statement call tothis.verifyends in.verified. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade tenvoy to 7.0.3ステージング環境で 7.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com