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 a vulnerability is introduced in rollup-plugin-styles@3.14.1:
Vulnerability CVE-2021-33587 affects package css-what (versions:<5.0.1): https://snyk.io/vuln/SNYK-JS-CSSWHAT-1298035
The above vulnerable package is referenced by rollup-plugin-styles@3.14.1 via: rollup-plugin-styles@3.14.1 ➔ 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
Since rollup-plugin-styles@3.14.1 (13,494 downloads per week) is referenced by 27 downstream projects (e.g., padl 1.0.3 (latest version), microsite 1.2.2-next.0 (latest version), @quilted/sewing-kit-plugins 0.2.29 (latest version), snowpack-plugin-rollup-bundle 0.4.4 (latest version), @hashicorp/sentinel-codemirror 0.0.8 (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)@gem-mine/script-rollup@2.7.5 ➔ rollup-plugin-styles@3.14.1 ➔ 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
(2)padl@1.0.3 ➔ rollup-plugin-styles@3.14.1 ➔ 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 rollup-plugin-styles@3.14.* 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 rollup-plugin-styles@3.14.1 ?
Fixing suggestions
In rollup-plugin-styles@3.14.2, maybe you can kindly try to 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
Thank you for your attention to this issue and welcome to share other ways to resolve the issue.
Best regards,
^_^
The text was updated successfully, but these errors were encountered:
Hi, @izevo @Anidetrix,
Issue Description
I noticed that a vulnerability is introduced in rollup-plugin-styles@3.14.1:
Vulnerability CVE-2021-33587 affects package css-what (versions:<5.0.1): https://snyk.io/vuln/SNYK-JS-CSSWHAT-1298035
The above vulnerable package is referenced by rollup-plugin-styles@3.14.1 via:
rollup-plugin-styles@3.14.1 ➔ 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
Since rollup-plugin-styles@3.14.1 (13,494 downloads per week) is referenced by 27 downstream projects (e.g., padl 1.0.3 (latest version), microsite 1.2.2-next.0 (latest version), @quilted/sewing-kit-plugins 0.2.29 (latest version), snowpack-plugin-rollup-bundle 0.4.4 (latest version), @hashicorp/sentinel-codemirror 0.0.8 (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)
@gem-mine/script-rollup@2.7.5 ➔ rollup-plugin-styles@3.14.1 ➔ 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
(2)
padl@1.0.3 ➔ rollup-plugin-styles@3.14.1 ➔ 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 rollup-plugin-styles@3.14.* 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 rollup-plugin-styles@3.14.1 ?
Fixing suggestions
In rollup-plugin-styles@3.14.2, maybe you can kindly try to 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
Thank you for your attention to this issue and welcome to share other ways to resolve the issue.
Best regards,
^_^
The text was updated successfully, but these errors were encountered: