# What is CVE-2023-7250? > CVE-2023-7250 is a medium-severity flaw (CVSS 5.3) in Iperf3 from Es, published on 18 March 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.9%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2023-7250 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 23 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 5.3 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.9% (latest exploit-likelihood forecast) - **Published:** 18 March 2024 - **Record last updated:** 17 June 2026 - **Main product:** Iperf3 from Es - **Affected products:** 5 ## What is CVE-2023-7250? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can slow it down. ### The official description A flaw was found in iperf, a utility for testing network performance using TCP, UDP, and SCTP. A malicious or malfunctioning client can send less than the expected amount of data to the iperf server, which can cause the server to hang indefinitely waiting for the remainder or until the connection gets closed. This will prevent other connections to the server, leading to a denial of service. ### What kind of flaw is it? - CWE-183: Permissive List of Allowed Inputs ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can slow it down Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L` ## Is CVE-2023-7250 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%. ### Timeline - 18 March 2024: Published - 17 June 2026: Record last updated ### How Precursor Intelligence ranks it CVE-2023-7250 scores **23 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2023-7250? The published record lists 5 products. Versions are as published: "before 3.15" means every version up to, but not including, 3.15. - [Iperf3](https://www.precursorintelligence.com/product/es/iperf3) by [Es](https://www.precursorintelligence.com/vendors/es) (Application): before 3.15 - [Enterprise Linux](https://www.precursorintelligence.com/product/redhat/enterprise_linux) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Operating system): 8.0, 9.0 - [Enterprise Linux for Arm 64](https://www.precursorintelligence.com/product/redhat/enterprise_linux_for_arm_64) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Operating system): 8.0_aarch64, 9.0_aarch64 - [Enterprise Linux for Ibm Z Systems](https://www.precursorintelligence.com/product/redhat/enterprise_linux_for_ibm_z_systems) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Operating system): 8.0_s390x, 9.0_s390x - [Enterprise Linux for Power Little Endian](https://www.precursorintelligence.com/product/redhat/enterprise_linux_for_power_little_endian) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Operating system): 8.0_ppc64le ## How do I fix CVE-2023-7250? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [access.redhat.com](https://access.redhat.com/errata/RHSA-2024:4241) (Third-party advisory) - [access.redhat.com](https://access.redhat.com/errata/RHSA-2024:9185) (Third-party advisory) - [access.redhat.com](https://access.redhat.com/security/cve/CVE-2023-7250) (Third-party advisory) - [bugzilla.redhat.com](https://bugzilla.redhat.com/show_bug.cgi?id=2244707) (Issue tracking, Third-party advisory) - [lists.debian.org](https://lists.debian.org/debian-lts-announce/2025/01/msg00027.html) ## Questions ### What is CVE-2023-7250? CVE-2023-7250 is a medium-severity flaw in Iperf3 from Es, published on 18 March 2024. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can slow it down. ### How serious is CVE-2023-7250? It scores 5.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2023-7250 is 23 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2023-7250 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2023-7250 affect? For Iperf3 from Es: before 3.15. The record lists 5 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2023-7250? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2023-7250 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact