You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that there is a vulnerability introduced in rollup-plugin-postcss@4.0.0:
As far as I am aware, vulnerability CVE-2021-33587 affects package css-what (versions:<5.0.1):https://snyk.io/vuln/SNYK-JS-CSSWHAT-1298035
Unfortunately, rollup-plugin-postcss@4.0.0 transitively depends on the vulnerable package via: rollup-plugin-postcss@4.0.0 ➔ cssnano@4.1.11 ➔ cssnano-preset-default@4.0.8 ➔ postcss-svgo@4.0.3 ➔ svgo@1.3.2 ➔ css-select@2.1.0 ➔ css-what@3.4.2
rollup-plugin-postcss@4.0.0 is so popular that lots of downstream projects depend on it (34,859 downloads per week, and about 359 downstream projects, e.g., microbundle 0.13.3 (latest version), @backstage/cli 0.7.3 (latest version), @types/rollup-plugin-postcss 3.1.4 (latest version), @nstudio/web 12.5.1 (latest version), @nstudio/web-angular 12.5.1 (latest version)), the vulnerability CVE-2021-33587 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1) @1stg/lib-config@3.0.0 ➔ @pkgr/rollup@1.1.4 ➔ rollup-plugin-postcss@4.0.0 ➔ cssnano@4.1.11 ➔ cssnano-preset-default@4.0.8 ➔ postcss-svgo@4.0.3 ➔ svgo@1.3.2 ➔ css-select@2.1.0 ➔ css-what@3.4.2 ......
If you remove the vulnerable package from rollup-plugin-postcss@4.0.0, 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 rollup-plugin-postcss@4.0.0 ?
Fixing suggestions
In rollup-plugin-postcss@4.0.*, you can kindly perform the following upgrade : cssnano ^4.1.10 ➔ ^5.0.0;
Note: cssnano@5.0.0(>=5.0.0-rc.0) transitively depends on css-what@5.0.1 which has fixed the vulnerability (CVE-2021-33587).
If you have any other ways to resolve the issue, you are welcome to share with me.^_^
Thanks again for your contributions to the downstream users!
Best regards,
Paimon
The text was updated successfully, but these errors were encountered:
Hi, @egoist @SASUKE40,
Issue Description
I noticed that there is a vulnerability introduced in rollup-plugin-postcss@4.0.0:
As far as I am aware, vulnerability CVE-2021-33587 affects package css-what (versions:<5.0.1):https://snyk.io/vuln/SNYK-JS-CSSWHAT-1298035
Unfortunately, rollup-plugin-postcss@4.0.0 transitively depends on the vulnerable package via:
rollup-plugin-postcss@4.0.0 ➔ cssnano@4.1.11 ➔ cssnano-preset-default@4.0.8 ➔ postcss-svgo@4.0.3 ➔ svgo@1.3.2 ➔ css-select@2.1.0 ➔ css-what@3.4.2
rollup-plugin-postcss@4.0.0 is so popular that lots of downstream projects depend on it (34,859 downloads per week, and about 359 downstream projects, e.g., microbundle 0.13.3 (latest version), @backstage/cli 0.7.3 (latest version), @types/rollup-plugin-postcss 3.1.4 (latest version), @nstudio/web 12.5.1 (latest version), @nstudio/web-angular 12.5.1 (latest version)), the vulnerability CVE-2021-33587 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1)
@1stg/lib-config@3.0.0 ➔ @pkgr/rollup@1.1.4 ➔ rollup-plugin-postcss@4.0.0 ➔ cssnano@4.1.11 ➔ cssnano-preset-default@4.0.8 ➔ postcss-svgo@4.0.3 ➔ svgo@1.3.2 ➔ css-select@2.1.0 ➔ css-what@3.4.2
......
If you remove the vulnerable package from rollup-plugin-postcss@4.0.0, 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 rollup-plugin-postcss@4.0.0 ?
Fixing suggestions
In rollup-plugin-postcss@4.0.*, you can kindly perform the following upgrade :
cssnano ^4.1.10 ➔ ^5.0.0
;Note:
cssnano@5.0.0(>=5.0.0-rc.0) transitively depends on css-what@5.0.1 which has fixed the vulnerability (CVE-2021-33587).
If you have any other ways to resolve the issue, you are welcome to share with me.^_^
Thanks again for your contributions to the downstream users!
Best regards,
Paimon
The text was updated successfully, but these errors were encountered: