DotVVM: ReDOS in routing
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| riganti | dotvvm | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Riganti | Dotvvm |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.577% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Riganti
Riganti dotvvm |
|
| Vendors & Products |
Riganti
Riganti dotvvm |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, a route containing multiple unconstrained parameters in one path segment can cause excessive regular-expression backtracking in DotvvmRoute.IsMatch when a remote requester supplies a long near-match path. DotvvmRouteParser.RouteRegex previously had no matching timeout. Patched runtimes retry with the .NET non-backtracking engine, while runtimes that do not support non-backtracking matching return HTTP 503 after the one-second timeout in DotvvmRoutingMiddleware. This issue is fixed in versions 4.2.11, 4.3.15, and 5.0.0-preview09-final. | |
| Title | DotVVM: ReDOS in routing | |
| Weaknesses | CWE-1333 | |
| References |
|
|
| Metrics |
cvssV4_0
|