Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

posibility of a 4.6.2 release with less strict ejs version dependency #739

Open
paimon0715 opened this issue Aug 10, 2021 · 0 comments
Open

Comments

@paimon0715
Copy link

Hi, @jamonholmgren, I'd like to report a vulnerability introduced by package [email protected]:

Issue Description

I noticed that a vulnerability is introduced in [email protected]:
Vulnerability SNYK-JS-EJS-1049328 affects package ejs (versions:<3.1.6): https://snyk.io/vuln/SNYK-JS-EJS-1049328
The above vulnerable package is referenced by [email protected] via:
[email protected][email protected]

Since [email protected] (14,538 downloads per week) is referenced by 98 downstream projects (e.g., solidarity 3.0.4 (latest version), @graphprotocol/graph-cli 0.21.1 (latest version), @shopware-pwa/cli 0.9.2 (latest version), @shopware-pwa/nuxt-module 0.9.2 (latest version), @dzlzv/hydra-cli 3.0.0 (latest version)), the vulnerability SNYK-JS-EJS-1049328 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1)@bethaged/[email protected][email protected][email protected]
(2)@kraken.js/[email protected][email protected][email protected]
......

If [email protected].* removes the vulnerable package from the above version, then its fixed version can help downstream users decrease their pain.

Given the large number of downstream users, could you help update your package to remove the vulnerability from [email protected] ?

Fixing suggestions

In [email protected], maybe you can try to perform the following upgrade :
ejs ^2.6.1 ➔ ^3.1.6;

Note:
[email protected](>=3.1.6) has fixed the vulnerability SNYK-JS-EJS-1049328.
Of course, you are welcome to share other ways to resolve the issue.^_^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant