Issue:
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
Solution:
Initially, I attempted to update NextJS from v12.1.6 to v12.3.4 (which is the latest non-breaking change version), but this did not solve the issue because v12.3.4 uses PostCSS < 8.4.31. Therefore, I need to utilize the npm overrides feature.
Issue: An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
https://github.com/prismatic-io/embedded/security/dependabot/9
Solution: Initially, I attempted to update NextJS from v12.1.6 to v12.3.4 (which is the latest non-breaking change version), but this did not solve the issue because v12.3.4 uses PostCSS < 8.4.31. Therefore, I need to utilize the npm overrides feature.