# CVE-2024-28023: Hardcoded credentials in FOXMAN-UN

> Hardcoded credentials in the message queueing mechanism allow attackers to access sensitive information or execute arbitrary code.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mp2w-fjq2-347v

## What is CVE-2024-28023?

CVE-2024-28023 is a medium-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in the message queueing mechanism that if 
exploited can lead to the exposure of resources or functionality to 
unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-28023?


## How do I fix CVE-2024-28023?

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

## Is CVE-2024-28023 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28023 and fix it if it is affected.

What it is: CVE-2024-28023 is a medium-severity vulnerability in Hitachi Energy FOXMAN-UN, published on 11 Jun 2024. 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-2024-28023 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-2024-28023/ (Markdown: https://insights.sbomify.com/CVE-2024-28023/index.md)
```

## Sources

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

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