# CVE-2022-43442: Information disclosure in +F FS040U software

> Attackers can obtain plaintext login passwords to access the management console of FUJI SOFT FS040U software.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-8m8p-mfww-c2cg

## What is CVE-2022-43442?

CVE-2022-43442 is a medium-severity vulnerability in FUJI SOFT INCORPORATED +F FS040U software, published on 5 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Plaintext storage of a password vulnerability exists in +F FS040U software versions v2.3.4 and earlier, which may allow an attacker to obtain the login password of +F FS040U and log in to the management console.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Fsi Fs040u Firmware.

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

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

## Is CVE-2022-43442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43442 is a medium-severity vulnerability in FUJI SOFT INCORPORATED +F FS040U software, published on 5 Dec 2022. 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-43442 in the wild and no public exploit code.

Affected product: FUJI SOFT INCORPORATED +F FS040U software. 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-43442/ (Markdown: https://insights.sbomify.com/CVE-2022-43442/index.md)
```

## Sources

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

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