# CVE-2023-51599: Honeywell Saia PG5 Controls Suite Directory Traversal Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code via directory traversal in ZIP file parsing, requiring user interaction to open a malicious file.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-44j3-q6p8-p422

## What is CVE-2023-51599?

CVE-2023-51599 is a high-severity path traversal vulnerability in Honeywell Saia PG5 Controls Suite, published on 3 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Honeywell Saia PG5 Controls Suite Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Honeywell Saia PG5 Controls Suite. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of ZIP files. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the current user.
. Was ZDI-CAN-18412.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Honeywell Saia Pg5 Controls Suite.

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

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

## Is CVE-2023-51599 being exploited?

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

## Other vulnerabilities in Honeywell Saia PG5 Controls Suite

- [CVE-2022-30319](https://insights.sbomify.com/CVE-2022-30319/): Auth bypass in n/a (high 8.1)
- [CVE-2023-51603](https://insights.sbomify.com/CVE-2023-51603/): Honeywell Saia PG5 Controls Suite CAB File Parsing Directory Traversal Remote Code Execution Vulnerability (high 7.8)
- [CVE-2023-51600](https://insights.sbomify.com/CVE-2023-51600/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)
- [CVE-2023-51601](https://insights.sbomify.com/CVE-2023-51601/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)
- [CVE-2023-51602](https://insights.sbomify.com/CVE-2023-51602/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51599 is a high-severity path traversal vulnerability in Honeywell Saia PG5 Controls Suite, published on 3 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-51599 in the wild and no public exploit code.

Affected product: Honeywell Saia PG5 Controls Suite. 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-51599/ (Markdown: https://insights.sbomify.com/CVE-2023-51599/index.md)
```

## Sources

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

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