# CVE-2024-53580: Null dereference in n/a

> A segmentation violation in iperf allows attackers to cause a denial of service via the parameter exchange function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** ALSA-2025:0161, ALSA-2025:0168, AZL-54458, AZL-54504, BELL-CVE-2024-53580, CLSA-2025-1756928002, DEBIAN-CVE-2024-53580, GHSA-2w89-5px3-fvx6, MGASA-2025-0024, OESA-2025-1040, RHSA-2025:0161, RHSA-2025:0168, RHSA-2025:0346, RHSA-2025:0402, RHSA-2025:0403, RHSA-2025:0404, RHSA-2025:0440, RHSA-2025:0505, RHSA-2025:0548, RHSA-2025:0570, RLSA-2025:0161, RLSA-2025:0168, SUSE-SU-2025:0291-1, UBUNTU-CVE-2024-53580, openSUSE-SU-2025:14700-1

## What is CVE-2024-53580?

CVE-2024-53580 is a high-severity vulnerability in Netapp Hci Compute Node, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iperf v3.17.1 was discovered to contain a segmentation violation via the iperf_exchange_parameters() function.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-53580?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iperf3` | AlmaLinux:8 | All versions | 3.5-11.el8_10 |
| `iperf3` | AlmaLinux:9 | All versions | 3.9-13.el9_5.1 |
| `iperf3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-11.el8_10 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-11.el8_10 |
| `iperf3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-11.el8_10 |
| `iperf3` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-13.el9_5.1 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-13.el9_5.1 |
| `iperf3-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-13.el9_5.1 |
| `iperf3` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.1 |
| `iperf3-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.1 |
| `iperf3-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.1 |
| `iperf3` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.1 |
| `iperf3` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.1 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.1 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.1 |
| `iperf3` | Red Hat:rhel_els:7 | All versions | 0:3.1.7-3.el7_9.1 |
| `iperf3-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.1.7-3.el7_9.1 |
| `iperf3-devel` | Red Hat:rhel_els:7 | All versions | 0:3.1.7-3.el7_9.1 |
| `iperf3` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.5-7.el8_8.1 |
| `iperf3-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.5-7.el8_8.1 |
| `iperf3-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.5-7.el8_8.1 |
| `iperf3` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.9-10.el9_2.1 |
| `iperf3-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.9-10.el9_2.1 |
| `iperf3-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:3.9-10.el9_2.1 |
| `iperf3` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.1 |
| `iperf3-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.1 |
| `iperf3-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.1 |
| `iperf3` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |
| `iperf3-debuginfo` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:3.5-7.el8_4.1 |

Products: Es Iperf3, Netapp Hci Compute Node, Netapp Ontap 9.

## How do I fix CVE-2024-53580?

Apply the vendor's patch.

## Is CVE-2024-53580 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53580 exists.

## Other vulnerabilities in Netapp Hci Compute Node

- [CVE-2025-54351](https://insights.sbomify.com/CVE-2025-54351/): Memory corruption in iperf3 (high 8.9)
- [CVE-2025-54349](https://insights.sbomify.com/CVE-2025-54349/): Memory corruption in iperf3 (medium 6.5)
- [CVE-2024-26306](https://insights.sbomify.com/CVE-2024-26306/): Information disclosure in n/a (medium 5.9)
- [CVE-2023-7250](https://insights.sbomify.com/CVE-2023-7250/): Iperf3: possible denial of service (medium 5.3)
- [CVE-2025-54350](https://insights.sbomify.com/CVE-2025-54350/): Denial of service in iperf3 (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53580 and fix it if it is affected.

What it is: CVE-2024-53580 is a high-severity vulnerability in Netapp Hci Compute Node, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53580 exists.

Affected product: Netapp Hci Compute Node. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53580/ (Markdown: https://insights.sbomify.com/CVE-2024-53580/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53580
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53580
- OSV: https://osv.dev/vulnerability/CVE-2024-53580

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53580/
Summaries are generated and may contain mistakes; the official description above is the record.