GHSA-XW22-WV29-3299

Vulnerability from github – Published: 2021-04-06 17:29 – Updated: 2021-04-02 17:05
VLAI?
Summary
ApiKey secret could be revelated on network issue
Details

Impact

What kind of vulnerability is it? Who is impacted? Applications that are using node-etsy-client and reporting client error to the end user will offer api key value too

Patches

Has the problem been patched? What versions should users upgrade to?

creharmony/node-etsy-client#18 fixes this issue. This is fixed in node-etsy-client v0.3.0 and later.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Do not report or log etsy client error if you are using version <= v0.2.0

Update your version of node-etsy-client

References

Are there any links users can visit to find out more?

  • https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17

For more information

If you have any questions or comments about this advisory: * Open an issue in github.com/creharmony/node-etsy-client/issues

Severity ?
8.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.2.0"
      },
      "package": {
        "ecosystem": "npm",
        "name": "node-etsy-client"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-21421"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-209"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-04-02T17:05:21Z",
    "nvd_published_at": "2021-04-01T22:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\nApplications that are using node-etsy-client and reporting client error to the end user will offer api key value too\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\ncreharmony/node-etsy-client#18 fixes this issue. This is fixed in [node-etsy-client v0.3.0](https://github.com/creharmony/node-etsy-client/tree/v0.3.0) and later.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nDo not report or log etsy client error if you are using version \u003c= v0.2.0\n\nUpdate your version of node-etsy-client\n\n### References\n_Are there any links users can visit to find out more?_\n\n- https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [github.com/creharmony/node-etsy-client/issues](https://github.com/creharmony/node-etsy-client/issues/)",
  "id": "GHSA-xw22-wv29-3299",
  "modified": "2021-04-02T17:05:21Z",
  "published": "2021-04-06T17:29:52Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/creharmony/node-etsy-client/security/advisories/GHSA-xw22-wv29-3299"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-21421"
    },
    {
      "type": "WEB",
      "url": "https://github.com/creharmony/node-etsy-client/commit/b4beb8ef080366c1a87dbf9e163051a446acaa7d"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "ApiKey secret could be revelated on network issue"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.