Vulnerability-Lookup

CNVD-2021-44985

Vulnerability from cnvd - Published: 2021-06-25

Title

tEnvoy数据伪造问题漏洞

Description

tEnvoy是开源的一个软件包。用于node.js 和浏览器中的 PGP、NaCl 和 PBKDF2的散列、随机、加密、解密、签名、转换。 tEnvoy 7.0.3之前版本存在数据伪造问题漏洞。目前没有详细漏洞细节提供。

Severity

高

Patch Name

tEnvoy数据伪造问题漏洞的补丁

Patch Description

tEnvoy是开源的一个软件包。用于node.js 和浏览器中的 PGP、NaCl 和 PBKDF2的散列、随机、加密、解密、签名、转换。 tEnvoy 7.0.3之前版本存在数据伪造问题漏洞。目前没有详细漏洞细节提供。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

厂商已发布了漏洞修复程序，请及时关注更新： https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m

Reference

https://nvd.nist.gov/vuln/detail/CVE-2021-32685

Impacted products

Name
tEnvoy tEnvoy <7.0.3

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-32685"
    }
  },
  "description": "tEnvoy\u662f\u5f00\u6e90\u7684\u4e00\u4e2a\u8f6f\u4ef6\u5305\u3002\u7528\u4e8enode.js \u548c\u6d4f\u89c8\u5668\u4e2d\u7684 PGP\u3001NaCl \u548c PBKDF2\u7684\u6563\u5217\u3001\u968f\u673a\u3001\u52a0\u5bc6\u3001\u89e3\u5bc6\u3001\u7b7e\u540d\u3001\u8f6c\u6362\u3002\n\ntEnvoy 7.0.3\u4e4b\u524d\u7248\u672c\u5b58\u5728\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\u3002\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2021-44985",
  "openTime": "2021-06-25",
  "patchDescription": "tEnvoy\u662f\u5f00\u6e90\u7684\u4e00\u4e2a\u8f6f\u4ef6\u5305\u3002\u7528\u4e8enode.js \u548c\u6d4f\u89c8\u5668\u4e2d\u7684 PGP\u3001NaCl \u548c PBKDF2\u7684\u6563\u5217\u3001\u968f\u673a\u3001\u52a0\u5bc6\u3001\u89e3\u5bc6\u3001\u7b7e\u540d\u3001\u8f6c\u6362\u3002\r\n\r\ntEnvoy 7.0.3\u4e4b\u524d\u7248\u672c\u5b58\u5728\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\u3002\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "tEnvoy\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "tEnvoy tEnvoy \u003c7.0.3"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2021-32685",
  "serverity": "\u9ad8",
  "submitTime": "2021-06-16",
  "title": "tEnvoy\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e"
}

CVE-2021-32685 (GCVE-0-2021-32685)

Vulnerability from cvelistv5 – Published: 2021-06-16 00:25 – Updated: 2024-08-03 23:25

Title

Improper Verification of Cryptographic Signature in tenvoy

Summary

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`.

Severity

9.8 (Critical)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE

CWE-347 - Improper Verification of Cryptographic Signature

Assigner

GitHub_M mitre root

References

3 references

URL	Tags
https://github.com/TogaTech/tEnvoy/security/advis…	x_refsource_CONFIRM
https://github.com/TogaTech/tEnvoy/commit/a121b34…	x_refsource_MISC
https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
TogaTech	tEnvoy	Affected: < 7.0.3

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T23:25:31.108Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "tEnvoy",
          "vendor": "TogaTech",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 7.0.3"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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`."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-347",
              "description": "CWE-347: Improper Verification of Cryptographic Signature",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2021-06-16T00:25:11.000Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3"
        }
      ],
      "source": {
        "advisory": "GHSA-7r96-8g3x-g36m",
        "discovery": "UNKNOWN"
      },
      "title": "Improper Verification of Cryptographic Signature in tenvoy",
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2021-32685",
          "STATE": "PUBLIC",
          "TITLE": "Improper Verification of Cryptographic Signature in tenvoy"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "tEnvoy",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "\u003c 7.0.3"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "TogaTech"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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`."
            }
          ]
        },
        "impact": {
          "cvss": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          }
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "CWE-347: Improper Verification of Cryptographic Signature"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m",
              "refsource": "CONFIRM",
              "url": "https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m"
            },
            {
              "name": "https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b",
              "refsource": "MISC",
              "url": "https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b"
            },
            {
              "name": "https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3",
              "refsource": "MISC",
              "url": "https://github.com/TogaTech/tEnvoy/releases/tag/v7.0.3"
            }
          ]
        },
        "source": {
          "advisory": "GHSA-7r96-8g3x-g36m",
          "discovery": "UNKNOWN"
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2021-32685",
    "datePublished": "2021-06-16T00:25:11.000Z",
    "dateReserved": "2021-05-12T00:00:00.000Z",
    "dateUpdated": "2024-08-03T23:25:31.108Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.