CVE-2024-32866: Conform contains a Prototype Pollution Vulnerability in `parseWith...` function
Summary Conform allows the parsing of nested objects in the form of object.property. Due to an improper implementation of this feature, an attacker can exploit it to trigger prototype pollution by passing a crafted input to parseWith... functions.
Published Apr 23, 2024 · Updated Jun 10, 2024
Affected packages
@conform-to/dom
- Ecosystem
- npm
- Affected
- >= 1.0.0, <= 1.1.0
- Fixed in
- 1.1.1
- Check
npm ls @conform-to/dom
@conform-to/zod
- Ecosystem
- npm
- Affected
- >= 1.0.0, <= 1.1.0
- Fixed in
- 1.1.1
- Check
npm ls @conform-to/zod
@conform-to/yup
- Ecosystem
- npm
- Affected
- >= 1.0.0, <= 1.1.0
- Fixed in
- 1.1.1
- Check
npm ls @conform-to/yup
@conform-to/zod
- Ecosystem
- npm
- Affected
- < 0.9.2
- Fixed in
- 0.9.2
- Check
npm ls @conform-to/zod
@conform-to/yup
- Ecosystem
- npm
- Affected
- < 0.9.2
- Fixed in
- 0.9.2
- Check
npm ls @conform-to/yup
@conform-to/dom
- Ecosystem
- npm
- Affected
- < 0.9.2
- Fixed in
- 0.9.2
- Check
npm ls @conform-to/dom
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Conform allows the parsing of nested objects in the form of object.property. Due to an improper implementation of this feature, an attacker can exploit it to trigger prototype pollution by passing a crafted input to parseWith... functions.
PoC
const { parseWithZod } = require('@conform-to/zod');
const { z } = require("zod");
const param = new URLSearchParams("__proto__.pollution=polluted");
const schema = z.object({ "a": z.string() });
parseWithZod(param, { schema });
console.log("pollution:", ({}).pollution); // should print "polluted"Details
The invocation of the parseWithZod function in the above PoC triggers the setValue function through getSubmissionContext and parse, executing the following process, resulting in prototype pollution:
let pointer = value;
pointer.__proto__ = pointer.__proto__;
pointer = pointer.__proto__;
pointer.polluted = "polluted";This is caused by the lack of object existence checking on line 117 in formdata.ts, where the code only checks for the presence of pointer[key] without proper validation.
Impact
Applications that use conform for server-side validation of form data or URL parameters are affected by this vulnerability.
Credited to key-moon, vtsvetkov-splunk.
References
- https://github.com/edmundhung/conform/security/advisories/GHSA-624g-8qjg-8qxf
- https://github.com/edmundhung/conform/commit/4819d51b5a53fd5486fc85c17cdc148eb160e3de
- https://nvd.nist.gov/vuln/detail/CVE-2024-32866
- https://github.com/edmundhung/conform/blob/59156d7115a7207fa3b6f8a70a4342a9b24c2501/packages/conform-dom/formdata.ts#L117
- https://github.com/edmundhung/conform/commit/cb604dd58b99e2d12716d901a23bfca724e741ef
- https://github.com/advisories/GHSA-624g-8qjg-8qxf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
