CVE-2025-54351
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer overflow vulnerability exists in iperf versions prior to 3.19.1 in net.c. The vulnerability is triggered when the --skip-rx-copy option is used and involves improper handling of MSG_TRUNC flag in recv() calls, allowing potential memory corruption, code execution, or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify iperf3 installationRun 'iperf3 --version' or 'which iperf3' to locate the iperf3 binary and determine its installed versionAffected if Version is 3.19 (the affected version listed)
-
Verify the exact version numberCompare the output of 'iperf3 --version' to the affected range. Versions prior to 3.19.1 are vulnerableAffected if Version shows 3.19 or any version lower than 3.19.1
-
Check for --skip-rx-copy usage in scripts or command historySearch for '--skip-rx-copy' in shell history files, startup scripts, automation scripts, or cron jobs using grep -r 'skip-rx-copy' in relevant directoriesAffected if The --skip-rx-copy option is found in any active configuration or command invocation
-
Inspect running processes or service configurationsReview any service definitions, systemd unit files, or running process commands that invoke iperf3 to see if --skip-rx-copy is specifiedAffected if A running iperf3 process or defined service uses the --skip-rx-copy flag
User is affected if iperf3 version 3.19 is installed AND the --skip-rx-copy option is actively used in any configuration, script, or command.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade iperf to version 3.19.1 or later. Until the upgrade is completed, avoid using the --skip-rx-copy command-line option.
iperf3 3.19.1 or later
- 1. Check current iperf3 version by running: `iperf3 --version`
- 2. If version is 3.19 or earlier (before 3.19.1), upgrade iperf3 to version 3.19.1 or later using your system's package manager (e.g., `apt-get update && apt-get install iperf3` on Debian/Ubuntu, or `yum update iperf3` on RHEL/CentOS)
- 3. Alternatively, compile from source: download iperf3 3.19.1 from https://github.com/esnet/iperf/releases/tag/3.19.1, then run `./configure && make && make install`
- 4. After upgrade, verify the new version: `iperf3 --version`
- 5. Confirm the version shows 3.19.1 or later which contains the fix for the buffer overflow in net.c
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54351 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data