# CVE-2022-40984: Memory corruption in WTViewerE series

> An attacker can cause a denial of service in Yokogawa WTViewerE software by processing a file with a long name, triggering a stack-based buffer overflow.

- **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:** 24 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-w9r8-q59v-7xx4

## What is CVE-2022-40984?

CVE-2022-40984 is a critical memory corruption vulnerability in Yokogawa Test & Measurement Corporation WTViewerE series, published on 24 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in WTViewerE series WTViewerE 761941 from 1.31 to 1.61 and WTViewerEfree from 1.01 to 1.52 allows an attacker to cause the product to crash by processing a long file name.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Yokogawa Wtviewere 761941, Yokogawa Wtviewerefree.

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

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

## Is CVE-2022-40984 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40984 is a critical memory corruption vulnerability in Yokogawa Test & Measurement Corporation WTViewerE series, published on 24 Oct 2022. 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-2022-40984 in the wild and no public exploit code.

Affected product: Yokogawa Test & Measurement Corporation WTViewerE series. 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-40984/ (Markdown: https://insights.sbomify.com/CVE-2022-40984/index.md)
```

## Sources

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

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