{"answers":{"affected":"2 open source packages ship an affected version, including tenvoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32685 in the wild and no public exploit code.","fix":"Upgrade tenvoy to 7.0.3 or later.","what":"CVE-2021-32685 is a critical vulnerability in TogaTech tEnvoy, published on 16 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32685 and fix it if it is affected.\n\nWhat it is: CVE-2021-32685 is a critical vulnerability in TogaTech tEnvoy, published on 16 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32685 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tenvoy (npm): affected all versions; fixed in 7.0.3\n- tenvoy (npm): affected all versions; fixed in 7.0.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-32685/ (Markdown: https://insights.sbomify.com/CVE-2021-32685/index.md)","id":"CVE-2021-32685","markdown":"https://insights.sbomify.com/CVE-2021-32685/index.md","name":"CVE-2021-32685","record":{"aliases":["GHSA-7r96-8g3x-g36m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript crypto library","requires_auth":"none","summary":"Attackers can bypass cryptographic signature verification in tEnvoy, allowing them to forge valid signatures for arbitrary messages.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tenvoy","vendor":"togatech"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"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`.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Verification of Cryptographic Signature in tenvoy","id":"CVE-2021-32685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of Service in PJSIP","id":"CVE-2021-32686"},"packages":[{"ecosystem":"npm","fixed":["7.0.3"],"introduced":["0"],"last_affected":[],"package":"tenvoy","purl":null,"source":"GHSA-7r96-8g3x-g36m"},{"ecosystem":"npm","fixed":["7.0.3"],"introduced":["0"],"last_affected":[],"package":"tenvoy","purl":"pkg:npm/tenvoy","source":"GHSA-7r96-8g3x-g36m"}],"prev":{"headline":"Missing Handler in @scandipwa/magento-scripts","id":"CVE-2021-32684"},"products":["tEnvoy"],"published":"2021-06-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["TogaTech"]},"summary":"Attackers can bypass cryptographic signature verification in tEnvoy, allowing them to forge valid signatures for arbitrary messages.","url":"https://insights.sbomify.com/CVE-2021-32685/"}