# CVE-2022-4258: Hima: Unquoted path vulnerabilities in HIMA PC based Software

> Local attackers can gain full system access by exploiting unquoted search paths in HIMA PC software via malicious executables.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-m3pf-3vpc-6m5j

## What is CVE-2022-4258?

CVE-2022-4258 is a high-severity vulnerability in HIMA HOPCS, published on 16 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In multiple versions of HIMA PC based Software an unquoted Windows search path vulnerability might allow local users to gain privileges via a malicious .exe file and gain full access to the system.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2022-4258?

It affects 4 products.


Products: Hima Hopcs, Hima X-Opc A\+e, Hima X-Opc Da, Hima X-Ots.

## How do I fix CVE-2022-4258?

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

## Is CVE-2022-4258 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4258 and fix it if it is affected.

What it is: CVE-2022-4258 is a high-severity vulnerability in HIMA HOPCS, published on 16 Jan 2023. 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-2022-4258 in the wild and no public exploit code.

Affected product: HIMA HOPCS. 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-2022-4258/ (Markdown: https://insights.sbomify.com/CVE-2022-4258/index.md)
```

## Sources

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

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