Universal Forwarder vulnerabilitiesRanked by how likely they are to be used.
Universal Forwarder is made by Splunk. We track 61 published vulnerabilities in it, across 47 versions. None of them is on the list of flaws known to be exploited today. If you run Universal Forwarder, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Universal Forwarder vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Universal Forwarder's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Universal Forwarder 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.
- 64%CVE-2021-22901High
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection.
- 36%CVE-2022-32206Medium
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms.
- 31%CVE-2022-32205Medium
A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.
- 23%CVE-2022-35737High
SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.
- 18%CVE-2021-30560High
Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- 17%CVE-2022-43551High
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP.
- 15%CVE-2021-22926High
libcurl-using applications can ask for a specific client certificate to be used in a transfer.
- 12%CVE-2022-32207Critical
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename...
- 9.8%CVE-2020-8285High
curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.
- 8.4%CVE-2022-32208Medium
When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly.
Running Universal Forwarder? 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
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.
- Matched to
- Universal Forwarder 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.
We track 61 published vulnerabilities listed under the name Universal Forwarder, across 47 versions.
None of Universal Forwarder's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Universal Forwarder. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.