undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `http://127.0.0.1` or `//127.0.0.1` ```js const undici = require("undici") undici.request({origin: "http://example.com", pathname: "//127.0.0.1"}) ``` Instead of processing the request as `http://example.org//127.0.0.1` (or `http://example.org/http://127.0.0.1` when `http://127.0.0.1 is used`), it actually processes the request as `http://127.0.0.1/` and sends it to `http://127.0.0.1`. If a developer passes in user input into `path` parameter of `undici.request`, it can result in an _SSRF_ as they will assume that the hostname cannot change, when in actual fact it can change because the specified path parameter is combined with the base URL. This issue was fixed in `undici@5.8.1`. The best workaround is to validate user input before passing it to the `undici.request` call.
References
Link | Resource |
---|---|
https://github.com/nodejs/undici/security/advisories/GHSA-8qr4-xgw6-wmr3 | Exploit Mitigation Third Party Advisory |
https://github.com/nodejs/undici/releases/tag/v5.8.2 | Release Notes Third Party Advisory |
https://github.com/nodejs/undici/commit/124f7ebf705366b2e1844dff721928d270f87895 | Patch Third Party Advisory |
Configurations
Information
Published : 2022-08-12 16:15
Updated : 2023-01-18 14:15
NVD link : CVE-2022-35949
Mitre link : CVE-2022-35949
JSON object : View
CWE
CWE-918
Server-Side Request Forgery (SSRF)
Products Affected
nodejs
- undici