Prototype Pollution in parse-nested-form-data via `__proto__` in FormData field names
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| milamer | parse-nested-form-data | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Milamer | Parse-nested-form-data |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-xp7r-j8r6-j9h3 | parse-nested-form-data has Prototype Pollution via `__proto__` in FormData field names |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.315% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Milamer
Milamer parse-nested-form-data |
|
| Vendors & Products |
Milamer
Milamer parse-nested-form-data |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | parse-nested-form-data is a tiny node module for parsing FormData by name into objects and arrays. Prior to version 1.0.1, parseFormData() walks bracket and dot-notation FormData field names into nested objects without filtering reserved property keys. A single FormData field whose name begins with __proto__, or contains .__proto__. mid-path, causes the parser to traverse onto Object.prototype and assign properties there, polluting the prototype chain of every plain object in the running process. This issue has been patched in version 1.0.1. | |
| Title | Prototype Pollution in parse-nested-form-data via `__proto__` in FormData field names | |
| Weaknesses | CWE-1321 | |
| References |
| |
| Metrics |
cvssV3_1
|