Symfony: JsonPath Evaluates Attacker-Controlled Regular Expressions in match()/search() Without Limits — ReDoS
symfony · symfony json-path
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/json-path Packagist |
|
|
| symfony/symfony Packagist |
|
symfony · symfony json-path
| Product | Affected | Fixed in |
|---|---|---|
| symfony/json-path Packagist |
|
|
| symfony/symfony Packagist |
|
|
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 7.3.0-BETA1 until 7.4.12 and 8.0.12, the JsonPath component compiles attacker-controlled match() and search() filter patterns directly into preg_match() without a length cap, i-regexp restriction, or bounded backtracking, allowing catastrophic-backtracking expressions to pin worker CPU and cause denial of service. This issue is fixed in versions 7.4.12 and 8.0.12.
From the CVE record · GitHub_M
The JsonPath component passes attacker-controlled match() and search() filter patterns to preg_match() without limits on pattern length or backtracking. If an attacker can supply those patterns, a catastrophic-backtracking expression can pin worker CPU and cause denial of service; the input does not specify whether network access, authentication, or user interaction is required.
Teams using Packagist symfony/json-path or symfony/symfony versions >=7.3.0 <7.4.12 or >=8.0.0 <8.0.12 should check their dependencies.