# CVE-2023-38403: Integer overflow in n/a

> Attackers can trigger integer overflow and heap corruption in iperf3 via crafted length fields, potentially leading to code execution or denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2023
- **Updated:** 27 Nov 2024
- **Also known as:** ALPINE-CVE-2023-38403, ALSA-2023:4570, ALSA-2023:4571, AZL-27672, BELL-CVE-2023-38403, DEBIAN-CVE-2023-38403, DLA-3506-1, DSA-5455-1, GHSA-hgwq-wchh-f9vv, JLSEC-2026-759, MGASA-2023-0271, OESA-2023-1497, RHSA-2023:4326, RHSA-2023:4414, RHSA-2023:4415, RHSA-2023:4416, RHSA-2023:4431, RHSA-2023:4432, RHSA-2023:4570, RHSA-2023:4571, RLSA-2023:4570, RLSA-2023:4571, SUSE-SU-2023:2987-1, SUSE-SU-2023:3887-1, UBUNTU-CVE-2023-38403, USN-6431-2, USN-6431-3, openSUSE-SU-2024:13060-1

## What is CVE-2023-38403?

CVE-2023-38403 is a high-severity vulnerability in Apple Macos, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-38403?

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iperf3` | AlmaLinux:8 | All versions | 3.5-7.el8_8.alma |
| `iperf3` | AlmaLinux:9 | All versions | 3.9-10.el9_2.alma |
| `iperf3` | Red Hat:enterprise_linux:7::client | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:3.1.7-3.el7_9 |
| `iperf3` | Red Hat:enterprise_linux:7::server | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:3.1.7-3.el7_9 |
| `iperf3` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.1.7-3.el7_9 |
| `iperf3-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:3.1.7-3.el7_9 |
| `iperf3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-7.el8_8 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-7.el8_8 |
| `iperf3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-7.el8_8 |
| `iperf3` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-10.el9_2 |
| `iperf3-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-10.el9_2 |
| `iperf3-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-10.el9_2 |
| `iperf3` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.5-4.el8_1 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.5-4.el8_1 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:3.5-4.el8_1 |
| `iperf3` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:3.5-4.el8_2 |
| `iperf3` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:3.5-7.el8_4 |
| `iperf3` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.5-7.el8_6 |
| `iperf3-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.5-7.el8_6 |
| `iperf3-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.5-7.el8_6 |
| `iperf3` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:3.9-10.el9_0 |
| `iperf3-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:3.9-10.el9_0 |
| `iperf3-debugsource` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:3.9-10.el9_0 |

Products: Apple Macos, Debian Debian Linux, Es Iperf3, Fedoraproject Fedora, Netapp Clustered Data Ontap, Netapp Ontap Select Deploy Administration Utility.

## How do I fix CVE-2023-38403?

Upgrade to a fixed version.

## Is CVE-2023-38403 being exploited?

There is no known exploitation of CVE-2023-38403 in the wild and no public exploit code.

## Other vulnerabilities in Apple Macos

- [CVE-2026-65400](https://insights.sbomify.com/CVE-2026-65400/): Apple macOS Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2024-44146](https://insights.sbomify.com/CVE-2024-44146/): Security feature bypass in macOS (critical 10.0)
- [CVE-2024-44148](https://insights.sbomify.com/CVE-2024-44148/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-38586](https://insights.sbomify.com/CVE-2023-38586/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-40455](https://insights.sbomify.com/CVE-2023-40455/): Security feature bypass in macOS (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38403 and fix it if it is affected.

What it is: CVE-2023-38403 is a high-severity vulnerability in Apple Macos, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38403 in the wild and no public exploit code.

Affected product: Apple Macos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-38403/ (Markdown: https://insights.sbomify.com/CVE-2023-38403/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-38403
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-38403
- OSV: https://osv.dev/vulnerability/CVE-2023-38403

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-38403/
Summaries are generated and may contain mistakes; the official description above is the record.