# CVE-2023-5396: Memory corruption in Experion Server

> A stack overflow in Honeywell Experion Server allows remote code execution via malformed messages, requiring an upgrade to mitigate.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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:** 17 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g6wc-3gqf-hf3q

## What is CVE-2023-5396?

CVE-2023-5396 is a high-severity memory corruption vulnerability in Honeywell Experion Server, published on 17 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server receiving a malformed message creates connection for a hostname that may cause a stack overflow resulting in possible remote code execution. See Honeywell Security Notification for recommendations on upgrading and versioning.

Weakness: CWE-805 (Buffer Access with Incorrect Length Value)

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


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

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

## Is CVE-2023-5396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5396 is a high-severity memory corruption vulnerability in Honeywell Experion Server, published on 17 Apr 2024. 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-5396 in the wild and no public exploit code.

Affected product: Honeywell Experion Server. 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-5396/ (Markdown: https://insights.sbomify.com/CVE-2023-5396/index.md)
```

## Sources

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

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