# CVE-2022-1738: Fuji Electric D300win Out-of-bounds Read

> An out-of-bounds read in Fuji Electric D300win allows attackers to leak sensitive data from process memory.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-gxh7-w5hf-9hgw

## What is CVE-2022-1738?

CVE-2022-1738 is a high-severity vulnerability in Fuji Electric D300win, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fuji Electric D300win prior to version 3.7.1.17 is vulnerable to an out-of-bounds read, which could allow an attacker to leak sensitive data from the process memory.

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

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

It affects 1 product.


Products: Fujielectric D300win.

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

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

## Is CVE-2022-1738 being exploited?

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

## Other vulnerabilities in Fuji Electric D300win

- [CVE-2022-1523](https://insights.sbomify.com/CVE-2022-1523/): Fuji Electric D300win Write-what-where condition (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1738 is a high-severity vulnerability in Fuji Electric D300win, published on 19 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-1738 in the wild and no public exploit code.

Affected product: Fuji Electric D300win. 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-1738/ (Markdown: https://insights.sbomify.com/CVE-2022-1738/index.md)
```

## Sources

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

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