CVE-2025-54350: Medium severity iperf iperf vulnerability
Published Aug 3, 2025
·Updated
In iperf before 3.19.1, iperfauth.c has a Base64Decode assertion failure and application exit upon a malformed authentication attempt.
Affected Software
5 affected componentsFixes available
iperf iperf<3.19.1
es iperf3>=3.2<3.19.1
Microsoft azl3 iperf3 3.17.1-3
Microsoft cbl2 iperf3 3.18-2
Microsoft cbl2 iperf3 3.18-1
Remediation
Event History
Aug 3, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·10:37 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·10:37 AM
Affected Software
Updated
via Microsoft·10:37 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-54350?
CVE-2025-54350 has a medium severity rating due to its impact on application stability.
2
How do I fix CVE-2025-54350?
To fix CVE-2025-54350, upgrade iperf to version 3.19.1 or later.
3
What kind of issue does CVE-2025-54350 present?
CVE-2025-54350 presents an assertion failure leading to application exit upon a malformed authentication attempt.
4
Which versions of iperf are affected by CVE-2025-54350?
CVE-2025-54350 affects all iperf versions prior to 3.19.1.
5
Who is the vendor for CVE-2025-54350?
The vendor for CVE-2025-54350 is Iperf.