Es vulnerabilitiesNone on the known-exploited list.
Es has 8 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 Iperf3, with 8. If you run Es software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Es products have the most vulnerabilities?
Iperf3 leads with 8 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Es vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Es's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Es 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.
- 7.0%CVE-2016-4303Critical
The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a non-hex character in a JSON...
- 2.0%CVE-2023-38403High
iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.
- 1.1%CVE-2024-26306Medium
iPerf3 before 3.17, when used with OpenSSL before 3.2.0 as a server with RSA authentication, allows a timing side channel in RSA decryption operations.
- 0.9%CVE-2023-7250Medium
A flaw was found in iperf, a utility for testing network performance using TCP, UDP, and SCTP.
- 0.9%CVE-2024-53580High
iperf v3.17.1 was discovered to contain a segmentation violation via the iperf_exchange_parameters() function.
- 0.4%
In iperf before 3.19.1, iperf_auth.c has a Base64Decode assertion failure and application exit upon a malformed authentication attempt.
- 0.4%CVE-2025-54349Medium
In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.
- 0.4%CVE-2025-54351High
In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).
All Es 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 Es? 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 parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a non-hex character in a JSON string, which triggers a heap-based buffer overflow.
- Matched to
- Es 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 8 published vulnerabilities across 1 product and 48 versions from Es.
None of Es's vulnerabilities is on the list of flaws known to be exploited today.
Iperf3, with 8 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Es 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.