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

Could you help update postcss in 1.2.3 release? #69

Open
bestrivens001 opened this issue Sep 3, 2021 · 0 comments
Open

Could you help update postcss in 1.2.3 release? #69

bestrivens001 opened this issue Sep 3, 2021 · 0 comments

Comments

@bestrivens001
Copy link

Hi, @leodido,

Issue Description

I noticed that a vulnerability is introduced in [email protected]:
Vulnerability CVE-2021-23382 affects package postcss (versions:<7.0.36,>=8.0.0 <8.2.13): https://snyk.io/vuln/SNYK-JS-POSTCSS-1255640
The above vulnerable package is referenced by [email protected] via:
[email protected][email protected]

Since [email protected] (7,316 downloads per week) is referenced by 21 downstream projects (e.g., h5p-nodejs-library 6.2.0 (latest version), nyc-lib 1.4.43 (latest version), @lipemat/js-boilerplate 6.6.0 (latest version), @lumieducation/h5p-html-exporter 8.1.4 (latest version), ah-veeva-exporter 1.4.2 (latest version)), the vulnerability CVE-2021-23382 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1)@ioiotv/[email protected] ➔ @ioiotv/[email protected][email protected][email protected]
(2)[email protected][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 kindly try to perform the following upgrade :
postcss ^6.x ➔ ^7.x;

Note:
[email protected](>=7.0.36 <8.0.0) has fixed the vulnerability CVE-2021-23382.
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