# CVE-2018-5442: Memory corruption in Fuji Electric V-Server VPR

> A stack-based buffer overflow in Fuji Electric V-Server VPR allows remote attackers to execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9x64-xcvq-38qc

## What is CVE-2018-5442?

CVE-2018-5442 is a critical memory corruption vulnerability in Fuji Electric V-Server VPR, published on 5 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Stack-based Buffer Overflow issue was discovered in Fuji Electric V-Server VPR 4.0.1.0 and prior. The stack-based buffer overflow vulnerability has been identified, which may allow remote code execution.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2018-5442?

It affects 1 product.


Products: Fujielectric V-Server Vpr Firmware.

## How do I fix CVE-2018-5442?

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

## Is CVE-2018-5442 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5442 and fix it if it is affected.

What it is: CVE-2018-5442 is a critical memory corruption vulnerability in Fuji Electric V-Server VPR, published on 5 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-5442 in the wild and no public exploit code.

Affected product: Fuji Electric V-Server VPR. 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-2018-5442/ (Markdown: https://insights.sbomify.com/CVE-2018-5442/index.md)
```

## Sources

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

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