# CVE-2022-3928: Hardcoded credential is found in the message queue

> Attackers can access internal message queue data due to hardcoded credentials in Hitachi Energy network management products.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-vgqf-5fqh-5xqq

## What is CVE-2022-3928?

CVE-2022-3928 is a high-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 5 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hardcoded credential is found in affected products' message queue. An attacker that manages to exploit this vulnerability will be able to access data to the internal message queue.

This issue affects 

  *  FOXMAN-UN product: FOXMAN-UN R15B, FOXMAN-UN R15A, FOXMAN-UN R14B, FOXMAN-UN R14A, FOXMAN-UN R11B, FOXMAN-UN R11A, FOXMAN-UN R10C, FOXMAN-UN R9C; 
  *  UNEM product: UNEM R15B, UNEM R15A, UNEM R14B, UNEM R14A, UNEM R11B, UNEM R11A, UNEM R10C, UNEM R9C.

List of CPEs: 
  *  cpe:2.3:a:hitachienergy:foxman-un:R15B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:foxman-un:R15A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R14B:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R14A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R11B:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R11A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R10C:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:foxman-un:R9C:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R15B:*:*:*:*:*:*:*

  *  cpe:2.3:a:hitachienergy:unem:R15A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R14B:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R14A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R11B:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R11A:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R10C:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:unem:R9C:*:*:*:*:*:*:*

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


Products: Hitachienergy Foxman-Un, Hitachienergy Unem.

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

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

## Is CVE-2022-3928 being exploited?

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

## Other vulnerabilities in Hitachi Energy FOXMAN-UN

- [CVE-2024-2013](https://insights.sbomify.com/CVE-2024-2013/): Auth bypass in FOXMAN-UN (critical 10.0)
- [CVE-2024-2012](https://insights.sbomify.com/CVE-2024-2012/): Auth bypass in FOXMAN-UN (critical 9.1)
- [CVE-2024-2011](https://insights.sbomify.com/CVE-2024-2011/): Memory corruption in FOXMAN-UN (high 8.6)
- [CVE-2022-3929](https://insights.sbomify.com/CVE-2022-3929/): Communication between the client and server partially using CORBA over TCP/IP (high 8.3)
- [CVE-2024-28020](https://insights.sbomify.com/CVE-2024-28020/): Hardcoded credentials in FOXMAN-UN (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3928 is a high-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 5 Jan 2023. 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-3928 in the wild and no public exploit code.

Affected product: Hitachi Energy FOXMAN-UN. 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-3928/ (Markdown: https://insights.sbomify.com/CVE-2022-3928/index.md)
```

## Sources

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

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