Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-xw22-wv29-3299
No affected components available
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
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard