CVE-2025-54349 Memory corruption in iperf3
An off-by-one error in iperf allows heap-based buffer overflows, potentially enabling remote code execution or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-54349?
CVE-2025-54349 is a medium-severity memory corruption vulnerability in ES iperf3, published on 3 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.
Weakness: CWE-193
Which versions are affected by CVE-2025-54349?
It affects 1 product.
Linux distribution packages (40)
iperf3 AlmaLinux:10 | All versions | 3.17.1-5.el10_1 |
iperf3 AlmaLinux:8 | All versions | 3.5-12.el8_10 |
iperf3 AlmaLinux:9 | All versions | 3.9-14.el9_7.1 |
iperf3 Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 |
iperf3-debuginfo Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 |
iperf3-debugsource Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 |
iperf3 Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 |
iperf3-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 |
iperf3-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 |
iperf3 Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 |
iperf3-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 |
iperf3-debugsource Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 |
iperf3 Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 |
iperf3-debuginfo Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 |
iperf3-debugsource Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 |
iperf3 Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 |
iperf3-debuginfo Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 |
iperf3-debugsource Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 |
iperf3 Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 |
iperf3-debuginfo Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 |
iperf3-debugsource Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 |
iperf3 Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3-debuginfo Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3-debugsource Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3 Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3-debuginfo Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3-debugsource Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 |
iperf3 Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 |
iperf3-debuginfo Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 |
iperf3-debugsource Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 |
iperf3 Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 |
iperf3-debuginfo Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 |
iperf3-debugsource Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 |
iperf3 Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 |
iperf3-debuginfo Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 |
iperf3-debugsource Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 |
iperf3 Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 |
iperf3-debuginfo Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 |
iperf3-debugsource Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 |
iperf3 Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.9-14.el9_6.1 |
Products include Es Iperf3.
How do I fix CVE-2025-54349?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-54349 being exploited?
There is no known exploitation of CVE-2025-54349 in the wild and no public exploit code.
Other vulnerabilities in ES iperf3
Sources
Also known as ALPINE-CVE-2025-54349, ALSA-2026:1592, ALSA-2026:1595, ALSA-2026:1597, AZL-66060, AZL-66065 and 20 more.