# CVE-2023-4601: Stack-based Buffer Overflow in NI System Configuration Software

> A stack-based buffer overflow in NI System Configuration allows attackers to execute arbitrary code or disclose information via crafted responses.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2023
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-9r4m-vc45-52hp

## What is CVE-2023-4601?

CVE-2023-4601 is a high-severity memory corruption vulnerability in NI System Configuration, published on 18 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in NI System Configuration that could result in information disclosure and/or arbitrary code execution. Successful exploitation requires that an attacker can provide a specially crafted response. This affects NI System Configuration 2023 Q3 and all previous versions.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Ni System Configuration.

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

No fix has been published for CVE-2023-4601 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-4601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4601 is a high-severity memory corruption vulnerability in NI System Configuration, published on 18 Oct 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-4601 in the wild and no public exploit code.

Affected product: NI System Configuration. 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-4601/ (Markdown: https://insights.sbomify.com/CVE-2023-4601/index.md)
```

## Sources

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

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