Server crash via malformed authentication token
Published Aug 3, 2025 · Updated Nov 3, 2025
Reachable assertion in ESnet iperf3 before 3.19.1 allows remote attackers to crash an authentication-enabled server via malformed credentials. Base64Decode passes the attacker-controlled authentication token to BIO_read, then asserts that the returned length equals a calculated decoded length; malformed Base64 violates that assumption and exits the process. Exploitation requires SSL authentication to be enabled and interrupts the server process, with no reported confidentiality or integrity impact.
Summary
What happened
Reachable assertion in ESnet iperf3 before 3.19.1 allows remote attackers to crash an authentication-enabled server via malformed credentials. Base64Decode passes the attacker-controlled authentication token to BIO_read, then asserts that the returned length equals a calculated decoded length; malformed Base64 violates that assumption and exits the process. Exploitation requires SSL authentication to be enabled and interrupts the server process, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2025-54350
- Published
- Aug 3, 2025
- Updated
- Nov 3, 2025
- Vendor
- ESnet
- Product
- iperf3
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.19.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo