body-parser vulnerable to denial of service when url encoding is used
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| body-parser | body-parser | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Expressjs | Body-parser | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wqch-xfxh-vrr4 | body-parser is vulnerable to denial of service when url encoding is used |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.392% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Expressjs
Expressjs body-parser |
|
| Vendors & Products |
Expressjs
Expressjs body-parser |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic. This issue is addressed in version 2.2.1. | |
| Title | body-parser vulnerable to denial of service when url encoding is used | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV4_0
|