-
Notifications
You must be signed in to change notification settings - Fork 69
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
Postcss 8 #198
Comments
It has also CVE before 8.2.10 |
I'm going to schedule this for The plan is to release and immediately supersede |
Note that discussion is split across this issue and PR #169 |
FWIW, this just popup on my screen:
|
CVE-2021-23368 for reference. |
We get postcss warnings instead pending bholloway/resolve-url-loader#198 dependency update.
There is an I will leave this issue open until we have full release of If you have tried the alpha and it works for you please 👍 here. |
Crossposting from #169 the alternative interrum fix is to force |
postcss released a backported fix as 7.0.36, currently waiting on the CVE to be updated. Can the dependency in |
3.1.4 was released with the upgraded dependency: #210 |
Just noting https://nvd.nist.gov/vuln/detail/CVE-2021-23382 - it would be good to get things updated. Hopefully with the work on v5 something can be released in the not too distant future. CVE-2021-23382 - moderate severity The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern /\s sourceMappingURL=(.*). |
Released |
It would be great if the resolve-url-loader could be migrated to use postcss 8. Postcss 7 is not maintained anymore.
The text was updated successfully, but these errors were encountered: