# CVE-2022-46360: Memory corruption in V-SFT and TELLUS

> A local attacker can execute arbitrary code or read sensitive information by tricking a user into opening a malicious image file in V-SFT or TELLUS.

- **Severity:** High 7.8 (`CVSS:3.1/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 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-hv42-mf2p-6599

## What is CVE-2022-46360?

CVE-2022-46360 is a high-severity memory corruption vulnerability in FUJI ELECTRIC CO., LTD. and Hakko Electronics Co., Ltd. V-SFT and TELLUS, published on 3 Jan 2023. 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

Out-of-bounds read vulnerability in V-SFT v6.1.7.0 and earlier and TELLUS v4.0.12.0 and earlier allows a local attacker to obtain the information and/or execute arbitrary code by having a user to open a specially crafted image file.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 2 products.


Products: Fujielectric Tellus, Fujielectric V-Sft.

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

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

## Is CVE-2022-46360 being exploited?

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

## Other vulnerabilities in FUJI ELECTRIC CO., LTD. and Hakko Electronics Co., Ltd. V-SFT and TELLUS

- [CVE-2026-8108](https://insights.sbomify.com/CVE-2026-8108/): Fuji Electric Tellus Exposed Dangerous Method or Function (high 7.8)
- [CVE-2023-47580](https://insights.sbomify.com/CVE-2023-47580/): Memory corruption in TELLUS (high 7.8)
- [CVE-2023-47581](https://insights.sbomify.com/CVE-2023-47581/): Memory corruption in TELLUS (high 7.8)
- [CVE-2023-47582](https://insights.sbomify.com/CVE-2023-47582/): Null dereference in TELLUS (high 7.8)
- [CVE-2023-47583](https://insights.sbomify.com/CVE-2023-47583/): Memory corruption in TELLUS Simulator (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46360 is a high-severity memory corruption vulnerability in FUJI ELECTRIC CO., LTD. and Hakko Electronics Co., Ltd. V-SFT and TELLUS, published on 3 Jan 2023. 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-2022-46360 in the wild and no public exploit code.

Affected product: FUJI ELECTRIC CO., LTD. and Hakko Electronics Co., Ltd. V-SFT and TELLUS. 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-46360/ (Markdown: https://insights.sbomify.com/CVE-2022-46360/index.md)
```

## Sources

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

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