# CVE-2024-8067: Unicode "best fit" argument injection

> An attacker can inject arguments via Unicode best fit mapping in Helix Core, potentially leading to code execution on the server.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-w72w-8rm9-6684

## What is CVE-2024-8067?

CVE-2024-8067 is a medium-severity command injection vulnerability in Helix Core, published on 24 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In versions of Helix Core prior to 2024.1 Patch 2 (2024.1/2655224) a Windows ANSI API Unicode "best fit" argument injection was identified.

Weakness: CWE-176 (Improper Handling of Unicode Encoding)

## Which versions are affected by CVE-2024-8067?


## How do I fix CVE-2024-8067?

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

## Is CVE-2024-8067 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8067 and fix it if it is affected.

What it is: CVE-2024-8067 is a medium-severity command injection vulnerability in Helix Core, published on 24 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8067 in the wild and no public exploit code.

Affected product: Helix Core. 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-2024-8067/ (Markdown: https://insights.sbomify.com/CVE-2024-8067/index.md)
```

## Sources

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

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