Iperf3: possible denial of service
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.93% (FIRST EPSS); higher than 59.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: iperf3 (AlmaLinux:8) 3.5-10.el8_10; iperf3 (AlmaLinux:9) 3.9-13.el9; iperf3 (Debian:11) 3.9-1+deb11u2.
Low priority for now. Upgrade to iperf3 (AlmaLinux:8) 3.5-10.el8_10; iperf3 (AlmaLinux:9) 3.9-13.el9; iperf3 (Debian:11) 3.9-1+deb11u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Mar 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 60th percentile
- CWE
- CWE-183
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| es | iperf3 | cpe:2.3:a:es:iperf3 |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | enterprise linux for arm 64 | cpe:2.3:o:redhat:enterprise_linux_for_arm_64 |
| redhat | enterprise linux for ibm z systems | cpe:2.3:o:redhat:enterprise_linux_for_ibm_z_systems |
| redhat | enterprise linux for power little endian | cpe:2.3:o:redhat:enterprise_linux_for_power_little_endian |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- es iperf3before 3.15
- redhat enterprise linux8.0
- redhat enterprise linux9.0
- redhat enterprise linux for arm 648.0_aarch64
- redhat enterprise linux for arm 649.0_aarch64
- redhat enterprise linux for ibm z systems8.0_s390x
- redhat enterprise linux for ibm z systems9.0_s390x
- redhat enterprise linux for power little endian8.0_ppc64le
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat Enterprise Linux 7
- all versionsunknown
Red Hat Red Hat Enterprise Linux 8
- 0:3.5-10.el8_10 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 9
- 0:3.9-13.el9 and laternot affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | iperf3 | before 3.5-10.el8_10 | 3.5-10.el8_10 |
| AlmaLinux:9 | iperf3 | before 3.9-13.el9 | 3.9-13.el9 |
| Debian:11 | iperf3 | before 3.9-1+deb11u2 | 3.9-1+deb11u2 |
| Debian:12 | iperf3 | all versions | — |
| Debian:13 | iperf3 | before 3.15-1 | 3.15-1 |
| Red Hat:enterprise_linux:8::appstream | iperf3 | before 0:3.5-10.el8_10 | 0:3.5-10.el8_10 |
| Red Hat:enterprise_linux:8::appstream | iperf3-debuginfo | before 0:3.5-10.el8_10 | 0:3.5-10.el8_10 |
| Red Hat:enterprise_linux:8::appstream | iperf3-debugsource | before 0:3.5-10.el8_10 | 0:3.5-10.el8_10 |
| Red Hat:enterprise_linux:9::appstream | iperf3 | before 0:3.9-13.el9 | 0:3.9-13.el9 |
| Red Hat:enterprise_linux:9::appstream | iperf3-debuginfo | before 0:3.9-13.el9 | 0:3.9-13.el9 |
| Red Hat:enterprise_linux:9::appstream | iperf3-debugsource | before 0:3.9-13.el9 | 0:3.9-13.el9 |
| Rocky Linux:8 | iperf3 | before 0:3.5-10.el8_10 | 0:3.5-10.el8_10 |
| Rocky Linux:9 | iperf3 | before 0:3.9-13.el9_5.1 | 0:3.9-13.el9_5.1 |
Same product
es: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-4303The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of ser41Plan
- CVE-2025-54351In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).40Plan
- CVE-2025-54349In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.40Plan
- CVE-2023-38403iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.31Monitor
- CVE-2024-53580iperf v3.17.1 was discovered to contain a segmentation violation via the iperf_exchange_parameters() function.30Monitor
- CVE-2024-26306iPerf3 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 23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:iperf3 | 3.5-10.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:iperf3 | 3.15-1 · Debian:13 | Package registry (OSV) |
| red hat:iperf3 | 0:3.5-10.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:iperf3-debuginfo | 0:3.5-10.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:iperf3-debugsource | 0:3.5-10.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:iperf3 | 0:3.5-10.el8_10 · Rocky Linux:8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-183 · Permissive List of Allowed InputsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Double EncodingCAPEC-120likelihood: Low · Medium
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Using Unicode Encoding to Bypass Validation LogicCAPEC-71likelihood: Medium · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.