Llhttp vulnerabilitiesNone on the known-exploited list.
Llhttp has 6 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Llhttp, with 6. If you run Llhttp software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Llhttp products have the most vulnerabilities?
Llhttp leads with 6 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Llhttp vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Llhttp's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Llhttp flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 82%CVE-2022-32214Medium
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests.
- 70%CVE-2022-32215Medium
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers.
- 46%CVE-2022-32213Medium
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).
- 3.2%CVE-2021-22959Medium
The parser in accepts requests with a space (SP) right after the header name before the colon.
- 2.8%CVE-2022-35256Medium
The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF.
- 2.5%CVE-2021-22960Medium
The parse function in llhttp < 2.1.4 and < 6.0.6.
All Llhttp products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Llhttp? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).
- Matched to
- Llhttp on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 6 published vulnerabilities across 1 product and 32 versions from Llhttp.
None of Llhttp's vulnerabilities is on the list of flaws known to be exploited today.
Llhttp, with 6 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Llhttp products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.