{"vulnerability": "cve-2022-35948", "sightings": [{"uuid": "b949dcf3-e69d-40f2-853b-9b3535f62b97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-35948", "type": "seen", "source": "https://t.me/ctinow/68259", "content": "Internet Bug Bounty: CVE-2022-35948: CRLF Injection in Nodejs \u2018undici\u2019 via Content-Type\n\nhttps://ift.tt/tek46IZ", "creation_timestamp": "2022-10-10T22:26:42.000000Z"}, {"uuid": "7aa0711b-b30f-485f-9a70-24804bf8b4ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-35948", "type": "published-proof-of-concept", "source": "https://t.me/cibsecurity/48129", "content": "\u203c CVE-2022-35948 \u203c\n\nundici is an HTTP/1.1 client, written from scratch for Node.js.`=&lt; undici@5.8.0` users are vulnerable to _CRLF Injection_ on headers when using unsanitized input as request headers, more specifically, inside the `content-type` header. Example: ``` import { request } from 'undici' const unsanitizedContentTypeInput = 'application/json\\r\\n\\r\\nGET /foo2 HTTP/1.1' await request('http://localhost:3000, { method: 'GET', headers: { 'content-type': unsanitizedContentTypeInput }, }) ``` The above snippet will perform two requests in a single `request` API call: 1) `http://localhost:3000/` 2) `http://localhost:3000/foo2` This issue was patched in Undici v5.8.1. Sanitize input when sending content-type headers using user input as a workaround.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-08-15T14:37:42.000000Z"}]}