esnet iperf3 up to 3.19.0 Base64Decode iperf_auth.c assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in esnet iperf3 up to 3.19.0. Affected by this issue is some unknown functionality of the file iperf_auth.c of the component Base64Decode Handler. Performing a manipulation results in assertion. This vulnerability is reported as CVE-2025-54350. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in esnet iperf3 up to 3.19.0. This affects an unknown functionality of the file iperf_auth.c of the component Base64Decode Handler. The manipulation with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. This is going to have an impact on availability. The summary by CVE is:
In iperf before 3.19.1, iperf_auth.c has a Base64Decode assertion failure and application exit upon a malformed authentication attempt.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-54350 since 07/21/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 253491 (TencentOS Server 4: iperf3 (TSSA-2025:0670)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 3.19.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 4eab661da0bbaac04493fa40164e928c6df7934a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (253491) and EUVD (EUVD-2025-23457). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CNA Base Score: 3.7
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 253491
Nessus Name: TencentOS Server 4: iperf3 (TSSA-2025:0670)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: iperf3 3.19.1
Patch: 4eab661da0bbaac04493fa40164e928c6df7934a
Timeline
07/21/2025 CVE reserved08/03/2025 Advisory disclosed
08/03/2025 VulDB entry created
08/21/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-54350 (🔒)
GCVE (CVE): GCVE-0-2025-54350
GCVE (VulDB): GCVE-100-318627
EUVD: 🔒
Entry
Created: 08/03/2025 11:44Updated: 08/21/2025 19:49
Changes: 08/03/2025 11:44 (67), 08/03/2025 21:40 (1), 08/05/2025 05:00 (1), 08/05/2025 18:47 (11), 08/21/2025 19:49 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.