CVE-2024-53580

Exp

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

Published: 2024-12-18 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-53580 is rated High Exploit Risk (60.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.23%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-53580

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-53580

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-26 0.69% 0.23% -0.46%
2 2026-01-25 0.56% 0.69% +0.13%
3 2026-01-22 — 0.56% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-53580

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-53580

OS Trackers for CVE-2024-53580

vendor priority summary link
alpine — CVE-2024-53580: 1 source package rows (iperf3); 3 state rows across 3 repos (3.20-main, 3.21-main, edge-main); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2024-53580
debian not yet assigned CVE-2024-53580 not yet assigned priority: Debian including 1 source packages (iperf3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-53580
redhat high — https://access.redhat.com/security/cve/CVE-2024-53580
suse medium CVE-2024-53580 severity moderate: SUSE including 15 source package names (iperf-3.18-1.1, iperf-3.18-150000.3.12.1, …), 36 product×package rows across 22 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (22 product lines)): Fixed 36. https://www.suse.com/security/cve/CVE-2024-53580/
ubuntu medium CVE-2024-53580 medium priority: Ubuntu including 2 source packages (iperf, iperf3), 17 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 4, released 4, not-affected 1. https://ubuntu.com/security/CVE-2024-53580

Affected software / configurations for CVE-2024-53580

Vendor Product Version Raw CPE
es iperf3 3.17.1 cpe:2.3:a:es:iperf3:3.17.1:*:*:*:*:*:*:*
netapp ontap_9 — cpe:2.3:a:netapp:ontap_9:-:*:*:*:*:*:*:*
netapp hci_compute_node — cpe:2.3:o:netapp:hci_compute_node:-:*:*:*:*:*:*:*

References for CVE-2024-53580

cvelogic Threat Intelligence