Skip to main content
No exploitation reportedFix available

CVE-2023-7250

Iperf3: possible denial of service

No exploitation reported by the sources we read.

  • Published2024-03-18
  • WeaknessCWE-183

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A flaw was found in iperf, a utility for testing network performance using TCP, UDP, and SCTP. A malicious or malfunctioning client can send less than the expected amount of data to the iperf server, which can cause the server to hang indefinitely waiting for the remainder or until the connection gets closed. This will prevent other connections to the server, leading to a denial of service.

Timeline

dates in UTC
  1. 2024-03-1812:21CVE publishedCNA

Versions per branch

NVD
Redhat enterprise linux
BranchAffectedFixed in
8.0= 8.0no fix published
9.0= 9.0no fix published
Redhat enterprise linux for arm 64
BranchAffectedFixed in
8.0= 8.0_aarch64no fix published
9.0= 9.0_aarch64no fix published
Redhat enterprise linux for ibm z systems
BranchAffectedFixed in
8.0= 8.0_s390xno fix published
9.0= 9.0_s390xno fix published

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA3 products

As redhat, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • iperf3Ubuntu:Pro:24.04:LTSall versions · fixed in 3.16-1ubuntu0.1~esm1
  • iperf3Ubuntu:Pro:20.04:LTSall versions · fixed in 3.7-3ubuntu0.1~esm1
  • iperf3Ubuntu:Pro:20.04:LTSall versions · fixed in 3.7-3ubuntu0.1~esm2
  • iperf3Ubuntu:Pro:18.04:LTSall versions · fixed in 3.1.3-1ubuntu0.1~esm1
  • iperf3Ubuntu:Pro:16.04:LTSall versions · fixed in 3.0.11-1ubuntu0.1~esm2
  • iperf3Ubuntu:25.10all versions · fixed in 3.18-2ubuntu0.1
  • iperf3Ubuntu:22.04:LTSall versions · fixed in 3.9-1+deb11u1ubuntu0.1
  • iperf3TuxCare:AlmaLinux:9.2all versions · fixed in 3.9-10.el9.alma.tuxcare.els1and 1 other package

17 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Published
2024-03-18
Last Modified
2026-11-05
NVD status
Modified
GitHub Advisory
GHSA-g636-8hgg-7gx9

Frequently asked questions

What is CVE-2023-7250?

A flaw was found in iperf, a utility for testing network performance using TCP, UDP, and SCTP. A malicious or malfunctioning client can send less than the expected amount of data to the iperf server, which can cause the server to hang indefinitely waiting for the remainder or until the connection gets closed. This will prevent other connections to the server, leading to a denial of service.

Is CVE-2023-7250 actively exploited?

Active exploitation of CVE-2023-7250 has not been confirmed. Its EPSS score was 0.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-7250?

CVE-2023-7250 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

Running iperf3? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record