Skip to content

Commit f819679

Browse files
1 parent de5e1b3 commit f819679

File tree

3 files changed

+22
-12
lines changed

3 files changed

+22
-12
lines changed

advisories/github-reviewed/2021/06/GHSA-5w25-hxp5-h8c9/GHSA-5w25-hxp5-h8c9.json

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-5w25-hxp5-h8c9",
4-
"modified": "2021-06-17T18:47:52Z",
4+
"modified": "2026-01-23T22:42:00Z",
55
"published": "2021-06-21T17:12:13Z",
6-
"aliases": [
7-
"CVE-2021-32685"
8-
],
9-
"summary": "Improper Verification of Cryptographic Signature",
10-
"details": "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`.",
6+
"withdrawn": "2026-01-23T22:42:00Z",
7+
"aliases": [],
8+
"summary": "Duplicate Advisory: Improper Verification of Cryptographic Signature",
9+
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-7r96-8g3x-g36m. This link is maintained to preserve external references.\n\n## Original Description\ntEnvoy 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`.",
1110
"severity": [
1211
{
1312
"type": "CVSS_V3",

advisories/github-reviewed/2021/06/GHSA-7r96-8g3x-g36m/GHSA-7r96-8g3x-g36m.json

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-7r96-8g3x-g36m",
4-
"modified": "2022-01-04T19:36:52Z",
4+
"modified": "2026-01-23T22:42:09Z",
55
"published": "2021-06-28T17:16:56Z",
6-
"aliases": [],
6+
"aliases": [
7+
"CVE-2021-32685"
8+
],
79
"summary": "Improper Verification of Cryptographic Signature",
8-
"details": "### Impact\nThe `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.\n\n### Patches\nUpgrade 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.\n\n### Workarounds\nIn `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) && `.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)\n",
10+
"details": "### Impact\nThe `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.\n\n### Patches\nUpgrade 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.\n\n### Workarounds\nIn `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) && `.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)",
911
"severity": [
1012
{
1113
"type": "CVSS_V3",
@@ -38,13 +40,21 @@
3840
"type": "WEB",
3941
"url": "https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m"
4042
},
43+
{
44+
"type": "ADVISORY",
45+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32685"
46+
},
4147
{
4248
"type": "WEB",
4349
"url": "https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b"
4450
},
4551
{
4652
"type": "PACKAGE",
4753
"url": "https://github.com/TogaTech/tEnvoy"
54+
},
55+
{
56+
"type": "WEB",
57+
"url": "https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3"
4858
}
4959
],
5060
"database_specific": {

advisories/github-reviewed/2022/02/GHSA-9chx-2vqw-8vq5/GHSA-9chx-2vqw-8vq5.json

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-9chx-2vqw-8vq5",
4-
"modified": "2022-02-08T16:08:49Z",
4+
"modified": "2026-01-23T22:41:41Z",
55
"published": "2022-02-01T00:01:00Z",
6+
"withdrawn": "2026-01-23T22:41:41Z",
67
"aliases": [
78
"CVE-2022-23409"
89
],
9-
"summary": "Path Traversal in the Logs plugin for Craft CMS",
10-
"details": "The Logs plugin before 3.0.4 for Craft CMS allows remote attackers to read arbitrary files via input to actionStream in Controller.php.",
10+
"summary": "Duplicate Advisory: Path Traversal in the Logs plugin for Craft CMS",
11+
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-fp63-499m-hq6m. This link is maintained to preserve external references.\n\n## Original Description\nThe Logs plugin before 3.0.4 for Craft CMS allows remote attackers to read arbitrary files via input to actionStream in Controller.php.",
1112
"severity": [
1213
{
1314
"type": "CVSS_V3",

0 commit comments

Comments
 (0)