# CVE-2023-6361: Memory corruption in WinHex

> Attackers can execute arbitrary code via a buffer overflow in WinHex triggered by a long filename argument.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-rqp6-8mfq-gp8w

## What is CVE-2023-6361?

CVE-2023-6361 is a high-severity memory corruption vulnerability in WinHex, published on 7 Oct 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

A vulnerability has been discovered in Winhex affecting version 16.1 SR-1 and 20.4. This vulnerability consists of a buffer overflow controlling the Structured Exception Handler (SEH) registers. This could allow attackers to execute arbitrary code via a long filename argument.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2023-6361 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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